Add required field validation to inline-repeater-interface#298
Merged
bryantgillespie merged 2 commits intoMar 3, 2026
Conversation
bryantgillespie
left a comment
bryantgillespie
left a comment
Contributor
There was a problem hiding this comment.
This is a nice improvement for sure! Thanks Rob.
bryantgillespie
approved these changes
Mar 3, 2026
bryantgillespie
deleted the
robl/cms-1665-require-to-be-set-on-validation-not-working-inline-repeater
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR wires the inline repeater into Directus's nested validation flow so that repeater sub-fields marked as required are enforced on save.
Because a repeater field can have multiple instances, I included the index number of the instance so it's clear which instance(s) is/are failing.