-
Notifications
You must be signed in to change notification settings - Fork 23
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
[EPIC] v0.6.x #592
Open
derekpierre
wants to merge
45
commits into
main
Choose a base branch
from
epic-v0.6.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
[EPIC] v0.6.x #592
Conversation
This file contains 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
✅ Deploy Preview for taco-demo canceled.
|
✅ Deploy Preview for taco-nft-demo canceled.
|
derekpierre
force-pushed
the
epic-v0.6.x
branch
2 times, most recently
from
October 10, 2024 17:41
bfef228
to
2a51cac
Compare
Update `JsonApiConditionSchema` to match lingo
… This is not directly exported, but is used internally by other conditions. Update compound condition to use common condition schema.
JSON path will always be able to be parsed. It only becomes invalid when combined with JSON, and this will only be known at decryption time.
… building blocks.
…s; It would be nice to have something common like this but I'm not sure how to do that currently. Explicitly define union of all conditions in compound and sequential modules.
…ted sequential conditions.
…not provided for conditionVariables.
…rror" is not present when success is true.
At @ts-expect-error annotation so that docs can build.
…etc. Add common single schema that encompasses all possible condition schemas.
…in the correct way.
Include jsonApiConditionSchema in anyConditionSchema.
…reuse of schemas (#591)
derekpierre
force-pushed
the
epic-v0.6.x
branch
from
October 15, 2024 19:34
5afedd8
to
7f30464
Compare
…dition exceeding max depth.
…` (nodes) are also valid in `taco-web` (client library).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type of PR:
Required reviews:
What this does
Candidate for next release of
@nucypher/tsco
.Issues fixed/closed:
SequentialCondition
#581taco-auth
in api docs #594IfThenElseCondition
#593Why it's needed:
Notes for reviewers: