Libraries tagged by marked
divante-ltd/pimcore5-clipboard
1638 Downloads
Clipboard Bundle for Pimcore 5. Adding objects to the special clipboard give you possibility to make actions only on some marked by you objects.
digu087/tcd-tagging
1010 Downloads
Use PHP traits to extend Laravel Eloquent Models to allow Tags. Models can be marked as Taggable. You can also assocaite a tag with multiple groups
boring-o11y/wirestan
37 Downloads
PHPStan rule for Livewire components: public properties that are never reassigned outside lifecycle methods must be marked #[Locked], so the client cannot tamper with them via $wire.set.
exoodev/yii2-marked
22 Downloads
The Marked extension for the Yii2 framework
cspray/marked-logs
524 Downloads
A PSR-3 Logger that will ensure all logs have their context marked with an identifier.
attus/markdown
10 Downloads
Markdown Field Formatter
xgc1986/finalizer
1660 Downloads
A simple utility library that checks for PHP classes that should or shouldn't be marked as final
temirkhan/phpstan-internal-rules
4 Downloads
PHPStan rules to prevent prohibited usage of classes marked as @internal
tagging/laravel-tagging
6 Downloads
Use PHP traits to extend Laravel Eloquent Models to allow Tags. Models can be marked as Taggable.
softtechnoes/laravel-tagging
27 Downloads
Use PHP traits to extend Laravel Eloquent Models to allow colorful Tags. Models can be marked as Taggable.
qmagix/laravel-tagging
21 Downloads
Use PHP traits to extend Laravel Eloquent Models to allow Tags. Models can be marked as Taggable. Derived from rtconner's work for compatibility with MySql 5.6
kossmoss/laravel-tagging
7 Downloads
Use PHP traits to extend Laravel Eloquent Models to allow Tags. Models can be marked as Taggable.
jasir/clipper
117 Downloads
Clips out marked parts from textfile
idevin/laravel-tagging
300 Downloads
Use PHP traits to extend Laravel Eloquent Models to allow Tags. Models can be marked as Taggable.
hallerweb/prioritize-php-client
3 Downloads
REST API of Prioritize, a resource, project and IoT orchestration platform. All endpoints live under /api/v1. From 1.0.0 on this REST surface is the stable public contract (SemVer); the Vaadin admin GUI and its @Route URLs are an implementation detail and NOT part of that promise. A few areas are marked 'experimental' in their schema and may still change within the 1.x line.