-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
chore: Strict request JSON check #37773
base: release
Are you sure you want to change the base?
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
This PR has not seen activitiy for a while. It will be closed in 7 days unless further activity is detected. |
This PR has been closed because of inactivity. |
Failed server tests
|
1 similar comment
Failed server tests
|
This PR has been closed because of inactivity. |
Failed server tests
|
This PR has not seen activitiy for a while. It will be closed in 7 days unless further activity is detected. |
Currently, if the incoming request body contains fields that aren't recognized by the backend, we just ignore them, and deserialize what we can. This has lead to subtle bugs and wasted a lot of developer time in the past, and added little value in return.
Most recently, with application creation, now fixed in #33722.
Another one, for action creation, client sends this in


eventData
field of the request body:But the class defined for
eventData
is this:Clearly isn't working.
This PR enabled the
FAIL_ON_UNKNOWN_PROPERTIES
setting only for the deserialization of HTTP request payloads. It shouldn't have impact on other deserializations like those for Git, and those that load resource files. Primarily to limit the scope.This should also bring in some much-needed type strictness to the client as well. So far, server has been lax in accepting just any fields in the incoming request body, so client was able to afford being lax about the object that was sent up.
Previously attempted at #33724.
Automation
/test sanity
🔍 Cypress test results
Warning
Tests have not run on the HEAD 1ac44e0 yet
Sat, 08 Feb 2025 01:21:41 UTC
Communication
Should the DevRel and Marketing teams inform users about this change?