relaticle/custom-fields
Laravel/Filament plugin to add dynamic custom fields to any Eloquent model without migrations. Includes 20+ field types, conditional visibility, tenant isolation, admin UI integration (forms/tables/infolists), CSV import/export, optional encryption, and extensible field types.
Is in → Is not in) reset the stored value to null, silently turning the condition into an "is in / is not in nothing" match. The value is now preserved whenever the new operator still takes one, and only cleared for value-less operators (is empty / is not empty) (#170).CustomFieldsPlugin::make()->sectionModalWidth(...) (a Width case or closure) or the custom-fields.management.section_modal_width config key. The default widens to screen-lg when section conditional visibility is enabled — previously the add-section modal stayed at 2xl, cramping the conditions row — and the create/edit modals now resolve to the same width (#170).Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.3.0...v3.4.0
SectionForm::extendSchemaUsing() — extend the custom-field section management form from application code (e.g. a service provider), with no subclassing or vendor patching. A single registration applies to both the Add and Edit section modals, and the callback receives the current schema plus the section's entity type, so extensions can be scoped per entity (#165).extra bag on CustomFieldSectionSettingsData — consumer-defined section settings bound under settings.extra.* now round-trip through the typed settings DTO (and through config import/export). Enables, for example, flagging a section to render as its own tab (#165).Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.2.1...v3.3.0
InfolistBuilder now evaluates each section's visibility against the record, mirroring the form path. Sections without conditions and field-level visibility are unaffected.Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.1.7...v3.2.0
Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.1.6...v3.1.7
postare/blade-mdi dependency with manukminasyan/blade-mdi, a Packagist-published fork that widens the illuminate/support constraint to include ^13.0. Same Postare\BladeMdi\ namespace, no source changes.composer require relaticle/custom-fields now works without extra setup.Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.1.4...v3.1.5
Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.1.3...v3.1.4
Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.1.2...v3.1.3
Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.1.1...v3.1.2
Full Changelog: https://github.com/relaticle/custom-fields/compare/v3.1.0...v3.1.1
normalizeValueForEvaluationaddslashes with json_encode for JS string escapinggetNormalizedFieldValuescreateSection actiongit ls-remote in changelog workflowFull Changelog: https://github.com/relaticle/custom-fields/compare/v3.0.14...v3.1.0
propaganistas/laravel-phonevendor/bin/custom-fields-upgrade)SYSTEM_SECTIONS feature flag for sectionless modelookup_type setting removed from text, number, date, and other non-relational field typesRun vendor/bin/custom-fields-upgrade to automatically migrate phone/email formats and lookup field settings.
CustomFields::form(), CustomFields::table(), CustomFields::infolist() builderscustom_field_options tableInteractsWithCustomFields trait moved to Relaticle\CustomFields\ConcernsCustomFieldsComponent::make()) in favor of builder APIHow can I help you explore Laravel packages today?