-
Notifications
You must be signed in to change notification settings - Fork 297
Hot Chocolate 15 Migration #2348
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
Conversation
|
@Aniruddh25, I will probably complete it this with whom shall I go through changes and questions? |
src/Service.Tests/Unittests/SerializationDeserializationTests.cs
Outdated
Show resolved
Hide resolved
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
Aniruddh25
left a comment
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.
LGTM, Thank you for this important upgrade!
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 6 pipeline(s). |
|
Just as input for the docs regarding the dateTime switch: the DateTime type follows the specification for the GraphQL DateTime scalar: https://www.graphql-scalars.com/date-time/ In previous versions, we allowed more date and time formats, including formats where the timezone was omitted. This could lead to data correctness issues, as consumers of the API might interpret the time differently than you intended. The specification is very precise about the required format and how a DateTime string must be provided. Take a look at the Test Cases section of the spec. With format checking enabled, we enforce compliance with the specified format. |
With Hot Chocolate 15 we have invested a lot into security, performance and GraphQL protocol standards. This PR will modernize the GraphQL stack of dab. - [X] Existing Regression tests --------- Co-authored-by: Aniruddh Munde <[email protected]>
With Hot Chocolate 15 we have invested a lot into security, performance and GraphQL protocol standards. This PR will modernize the GraphQL stack of dab. - [X] Existing Regression tests --------- Co-authored-by: Aniruddh Munde <[email protected]>
With Hot Chocolate 15 we have invested a lot into security, performance and GraphQL protocol standards. This PR will modernize the GraphQL stack of dab. - [X] Existing Regression tests --------- Co-authored-by: Aniruddh Munde <[email protected]>
## Why make this change? This change is made to add the Hot-Chocolate PR to the 1.5 branch ## What is this change? This change cherry picks the PRs related to Hot-Chocolate upgrade in order to add it to the branch 1.5. - #2681 - #2348 ## How was this tested? - [ ] Integration Tests - [ ] Unit Tests ## Sample Request(s) --------- Co-authored-by: Sezal Chug <[email protected]> Co-authored-by: sezalchug <[email protected]> Co-authored-by: Tommaso Stocchi <[email protected]> Co-authored-by: Aaron Powell <[email protected]> Co-authored-by: aaronburtle <[email protected]> Co-authored-by: Aniruddh Munde <[email protected]> Co-authored-by: Jerry Nixon <[email protected]> Co-authored-by: vadeveka <[email protected]> Co-authored-by: Michael Staib <[email protected]>
Why make this change?
With Hot Chocolate 15 we have invested a lot into security, performance and GraphQL protocol standards.
What is this change?
This PR will modernize the GraphQL stack of dab.
How was this tested?