coprocessor: Disable validation of data field inside GraphQL response
#7732
Conversation
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
|
@IvanGoncharov, please consider creating a changeset entry in |
IvanGoncharov
force-pushed
the
i1g/fix_subscription_data_validation
branch
from
e58cb2e to
64cb551
Compare
✅ Docs preview has no changesThe preview was not built because there were no changes. Build ID: 105145fe785740b0dddb694f |
IvanGoncharov
commented
Jun 19, 2025
|
|
||
| // FIXME(@IvanGoncharov): This function shouldn't exist, we should always validate `data` field | ||
| // At the moment, Router has many places that return empty object as a GraphQL Response so I temporary created a function that bypass this validation. | ||
| pub(crate) fn from_value_without_validating_data_field( |
There was a problem hiding this comment.
Here is the core change: I moved data validation into "proper" function and made a "workaround" function without this validation.
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.
Checklist
Complete the checklist (and note appropriate exceptions) before the PR is marked ready-for-review.
Exceptions
Note any exceptions here
Notes
Footnotes
It may be appropriate to bring upcoming changes to the attention of other (impacted) groups. Please endeavour to do this before seeking PR approval. The mechanism for doing this will vary considerably, so use your judgement as to how and when to do this. ↩
Configuration is an important part of many changes. Where applicable please try to document configuration examples. ↩
A lot of (if not most) features benefit from built-in observability and
debug-level logs. Please read this guidance on metrics best-practices. ↩Tick whichever testing boxes are applicable. If you are adding Manual Tests, please document the manual testing (extensively) in the Exceptions. ↩