[5.x] Asset validation rules as string in GraphQL, part 2#11790
Merged
jasonvarga merged 1 commit into5.xfrom May 14, 2025
Merged
[5.x] Asset validation rules as string in GraphQL, part 2#11790jasonvarga merged 1 commit into5.xfrom
jasonvarga merged 1 commit into5.xfrom
Conversation
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
1 participant
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 follows #11781. After merging had second thoughts about it.
Rather than just checking for
__toString, I thought it it should be a bit more explicit, so it now uses a contract and dedicated method.The fall back is now the class name with
::classsuffix.