-
Notifications
You must be signed in to change notification settings - Fork 529
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
Fix unicode bug with "format_raw_parse_error" sample #1044
Merged
binaryseed
merged 2 commits into
absinthe-graphql:master
from
mattbaker:parse-error-sample-truncation
Feb 10, 2021
+30
−1
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,6 +29,34 @@ defmodule Absinthe.Phase.ParseTest do | |
] == bp.execution.validation_errors | ||
end | ||
|
||
@graphql "aa;bbbbbbbb—cc" | ||
test "should provide sample of parsing failure respecting unicode boundary" do | ||
assert {:error, bp} = Absinthe.Phase.Parse.run(@graphql, jump_phases: false) | ||
|
||
assert [ | ||
%Absinthe.Phase.Error{ | ||
extra: %{}, | ||
locations: [%{column: 3, line: 1}], | ||
message: "Parsing failed at `;bbbbbbbb—`", | ||
phase: Absinthe.Phase.Parse | ||
} | ||
] == bp.execution.validation_errors | ||
end | ||
|
||
@graphql ";" | ||
test "should provide sample of parsing failure on very short query strings" do | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not something we experienced, but something that occurred to me when I was thinking about the binary pattern match. |
||
assert {:error, bp} = Absinthe.Phase.Parse.run(@graphql, jump_phases: false) | ||
|
||
assert [ | ||
%Absinthe.Phase.Error{ | ||
extra: %{}, | ||
locations: [%{column: 1, line: 1}], | ||
message: "Parsing failed at `;`", | ||
phase: Absinthe.Phase.Parse | ||
} | ||
] == bp.execution.validation_errors | ||
end | ||
|
||
@graphql """ | ||
query { | ||
user { | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're thinking character-oriented and not byte oriented I would expect 10 characters. In practice this test will fail because the message will include a sample of ten bytes.