Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.x] Add validation replacements to replicator and grid field types #10064

Conversation

florianbrinkmann
Copy link

@florianbrinkmann florianbrinkmann commented May 14, 2024

Currently it’s not possible to use the validation replacements (for example, validation_rule_handle:{id}) in fields that are part of replicator or grid fields, because the validator instance that is used for the »top-level« fields isn’t the same that’s used for the fields inside the replicator/grid (at least I think that’s the reason).

This PR changes that and adds the replacements for replicator and grid fields, if the parent is an Entry.

Closes #10065

@florianbrinkmann florianbrinkmann force-pushed the add-validator-replacements-to-replicator-and-grid branch from ebd9f9c to 5b8a4e2 Compare May 14, 2024 08:26
@duncanmcclean duncanmcclean changed the title [4.x] add validation replacements to replicator and grid field types [4.x] Add validation replacements to replicator and grid field types May 14, 2024
@duncanmcclean
Copy link
Member

We're no longer accepting fixes to 4.x, can you re-target this PR for 5.x?

Copy link
Member

@jasonvarga jasonvarga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

☝️ What Duncan said.

@jasonvarga
Copy link
Member

If this is still important for you, please feel free to update this PR to target 5.x and we can reopen. Or, open a fresh PR. Up to you. Thanks!

@jasonvarga jasonvarga closed this May 28, 2024
@florianbrinkmann
Copy link
Author

Will update it next week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants