fix(harmonizer): fix CompositionError exception to format properly#664
Merged
Conversation
duckki
force-pushed
the
duckki/fed-805-v2.9
branch
from
October 2, 2025 22:46
ac4a0fa to
bcce38c
Compare
tninesling
approved these changes
Oct 3, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes an issue where harmonizer (v2.9) returns a
INVALID_GRAPHQLerror without formatting the message correctly. The error message would looke like this:INVALID_GRAPHQL: [object Object].This PR adds a type check for
CompositionErrorand convert other types toCompositionError.