fix: accept scalar values in v2 visibility rules#293
Open
Conversation
Align the v2 visibility models with the schema so mustBe/ifNotIn accept numbers and booleans instead of rejecting valid descriptors during lint resolution. Made-with: Cursor
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.
Summary
mustBeandifNotInvisibility conditions to accept scalar values like numbers, booleans, and nullTest plan
PYTHONPATH=src python3 - <<'PY' ... field_with_visibility_conditions fixture conversion ... PYSupersedes #290 with a branch that lives directly on
LedgerHQ/python-erc7730, so normal upstream CI can run.Made with Cursor