fix min/max length constraint handling in Ash.Type for array types #2155
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
97a9121 to
e954af5
Compare
zachdaniel
reviewed
Jun 20, 2025
9f578b0 to
05089cd
Compare
zachdaniel
reviewed
Jun 20, 2025
zachdaniel
reviewed
Jun 21, 2025
3137e9a to
5404f75
Compare
Signed-off-by: kernel-io <[email protected]>
5404f75 to
bafa7c0
Compare
zachdaniel
approved these changes
Jun 26, 2025
Contributor
|
🚀 Thank you for your contribution! 🚀 |
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.
run the min/max length constraints for
{:array, _}types after all the other constraints have been applied