generated from TBD54566975/tbd-project-template
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Be strict with ingressed model objects, optionally #2132
Labels
Comments
Open
worstell
added a commit
that referenced
this issue
Aug 15, 2024
worstell
added a commit
that referenced
this issue
Aug 15, 2024
worstell
added a commit
that referenced
this issue
Aug 15, 2024
worstell
added a commit
that referenced
this issue
Aug 15, 2024
worstell
added a commit
that referenced
this issue
Aug 15, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 15, 2024
fixes #2132 adds support for `ftl:encoding` directive. the default `ftl:encoding` type is json and presently supports only the `lenient` option. `//ftl:encoding lenient` or `//ftl:encoding json lenient` (which are equivalent) can annotate an ingress verb. when an ingress verb is annotated with this, it will accept requests with unknown/extra fields and ignore them. --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relates to the fix for #2117 and #2119
We're currently lenient on inbound objects, which unblocks the client team, but they'd prefer to have it be optional. I.e. Jackson has:
@JsonIgnoreProperties(ignoreUnknown = true)
The text was updated successfully, but these errors were encountered: