-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: parse schema from SDL #3
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
2e01ff4
initial SDL implementation
JoviDeCroock 631f1f4
export functions
JoviDeCroock da4c3cf
fix input type definitions
JoviDeCroock cd93b2c
fix missing implementors
JoviDeCroock 6f50164
remove need for ParseResult
JoviDeCroock 2bdadb9
down to 1 failing test
JoviDeCroock 2b2245e
fix kitchen sink by adding possible_interface back, we should verify …
JoviDeCroock 9c3f4bc
bug found in build_client_schema
JoviDeCroock 3fc0179
validate
JoviDeCroock 89d4abc
more fixes
JoviDeCroock 97054f5
run clippy
JoviDeCroock be59c44
Update src/schema/build_client_schema.rs
JoviDeCroock 8a80e18
Update src/schema/build_client_schema.rs
JoviDeCroock 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
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
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
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 |
---|---|---|
@@ -0,0 +1,54 @@ | ||
use std::{error::Error, fmt::Display}; | ||
|
||
// Todo: Maybe reuse top level GraphQL/Syntax error struct? Would that be suitable? | ||
#[derive(Debug)] | ||
pub enum SchemaError { | ||
SyntaxError(String), | ||
ValidationError(String), | ||
} | ||
|
||
impl Display for SchemaError { | ||
fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result { | ||
match self { | ||
SchemaError::SyntaxError(s) => write!(f, "{}", s), | ||
SchemaError::ValidationError(s) => write!(f, "Validation error: {}", s), | ||
} | ||
} | ||
} | ||
|
||
impl Error for SchemaError {} | ||
|
||
macro_rules! syntax_err { | ||
($msg:literal, $($arg:tt)*) => { | ||
Err(syntax!($msg, $($arg)*)) | ||
}; | ||
|
||
($msg:literal) => { | ||
Err(syntax!($msg)) | ||
}; | ||
} | ||
|
||
macro_rules! syntax { | ||
($msg:literal, $($arg:tt)*) => { | ||
SchemaError::SyntaxError(format!($msg, $($arg)*)) | ||
}; | ||
|
||
($msg:literal) => { | ||
SchemaError::SyntaxError(format!($msg)) | ||
}; | ||
} | ||
|
||
macro_rules! validation { | ||
($msg:literal, $($arg:tt)*) => { | ||
SchemaError::ValidationError(format!($msg, $($arg)*)) | ||
}; | ||
|
||
($msg:literal) => { | ||
SchemaError::ValidationError(format!($msg)) | ||
}; | ||
} | ||
|
||
// Required for macro visibility. | ||
pub(crate) use syntax; | ||
pub(crate) use syntax_err; | ||
pub(crate) use validation; |
Oops, something went wrong.
Oops, something went wrong.
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.
Did you end up figuring out what's up here with the skips?