fix: make request_token and context optional based on skip parameters #168
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.
As specified in the Protecting Out-of-Band Actions section of the Castle documentation, if we need to make requests to the Filter/Risk API from the server side, we can pass the
skip_request_token_validation
orskip_context_validation
parameters to makerequest_token
andcontext
optional. However, this behavior is not currently reflected in the type definitions, so we have to use// @ts-expect-error
in our codebase.This merge request updates the models so that when any of these skip parameters are passed, the corresponding field becomes optional.