v3.5.3

What's Changed

Other Changes

• fix: keep multi-choice visibleJs expressions attribute-safe and id-typed by @ManukMinasyan in #178

Full Changelog: v3.5.2...v3.5.3

v3.5.2

What's Changed

Other Changes

• fix: evaluate multi-choice visibility conditions as exact option membership by @ManukMinasyan in #177

Full Changelog: v3.5.1...v3.5.2

v3.5.1

What's Changed

Other Changes

• fix: ignore validation for conditionally hidden custom fields by @ManukMinasyan in #176

Full Changelog: v3.5.0...v3.5.1

v3.5.0

What's Changed

Other Changes

• chore(deps): bump actions/checkout from 6 to 7 by @dependabot[bot] in #174
• fix(i18n): replace hardcoded UI strings with translation keys by @erikpach in #173
• feat: consumer hooks to scope field uniqueness + visibility picker by @ManukMinasyan in #175

Full Changelog: v3.4.1...v3.5.0

v3.4.1

Fixed

• Date validation "After another field" reference dropdown now populates when creating a field. The reference-field selector showed "No options available" while creating a new date custom field — it only worked when editing an existing one. The options closure resolved the entity type through the relative state path $get('../../../entity_type'), which inside the field-management action modal (mountedActions.0.data.*) climbed past the form-data scope to the Livewire root and returned null, short-circuiting to an empty list. It now resolves entity_type/code via absolute data-scope paths, correct in both the action-modal and page-form contexts (#172).

Full Changelog: v3.4.0...v3.4.1

v3.4.0

Fixed

• Visibility condition value no longer wiped when only the operator changes. Editing a saved section/field visibility condition and changing its operator (e.g. 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).

Added

• Configurable section modal width. The add/edit section modal width is now resolved through 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: v3.3.0...v3.4.0

v3.3.0

Added

• 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).
• Free-form 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: v3.2.1...v3.3.0

v3.2.1

Fixed

• Apply section-level conditional visibility on infolists (#162). Section-level visibility conditions (including cross-record relation conditions) were only honored on forms; on infolists a section rendered for every record whenever it had any visible field. InfolistBuilder now evaluates each section's visibility against the record, mirroring the form path. Sections without conditions and field-level visibility are unaffected.

v3.2.0

What's Changed

Other Changes

• chore(deps): bump fast-uri from 3.1.0 to 3.1.2 in /docs in the npm_and_yarn group across 1 directory by @dependabot[bot] in #152
• chore(deps): bump devalue from 5.8.0 to 5.8.1 in /docs in the npm_and_yarn group across 1 directory by @dependabot[bot] in #153
• chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates by @dependabot[bot] in #156
• chore(deps): bump brace-expansion from 2.1.0 to 5.0.6 in /docs in the npm_and_yarn group across 1 directory by @dependabot[bot] in #157
• chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates by @dependabot[bot] in #158
• chore(deps): bump hono from 4.12.18 to 4.12.23 in /docs in the npm_and_yarn group across 1 directory by @dependabot[bot] in #160
• fix: render tags-input infolist entries as badges by @ManukMinasyan in #155
• feat: cross-record (relation-path) visibility conditions [3.x] by @ManukMinasyan in #161

Full Changelog: v3.1.7...v3.2.0

v3.1.7

What's Changed

Other Changes

• chore(deps): bump ip-address from 10.1.0 to 10.2.0 in /docs in the npm_and_yarn group across 1 directory by @dependabot[bot] in #147
• chore(deps): bump the npm_and_yarn group across 1 directory with 3 updates by @dependabot[bot] in #148
• chore(deps): bump nuxt-og-image from 6.3.7 to 6.5.0 in /docs in the npm_and_yarn group across 1 directory by @dependabot[bot] in #150
• fix: prevent self-clear of field_code in visibility condition repeater by @erikpach in #146
• fix(phpstan): use covariant Model in Scope apply signatures for laravel 13 [3.x] by @ManukMinasyan in #151

New Contributors

• @erikpach made their first contribution in #146

Full Changelog: v3.1.6...v3.1.7