Update dev-session queries with new schema#6894
Merged
isaacroldan merged 1 commit intomainfrom Feb 25, 2026
Merged
Conversation
Contributor
|
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |
davejcameron
approved these changes
Feb 25, 2026
alfonso-noriega
approved these changes
Feb 25, 2026
Contributor
Coverage report
Test suite run success3768 tests passing in 1448 suites. Report generated by 🧪jest coverage report action from 80d5455 |
craigmichaelmartin
approved these changes
Feb 25, 2026
isaacroldan
deleted the
02-25-update_dev-session_queries_with_new_schema
branch
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
4 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.
WHY are these changes introduced?
The
updatedAtfield in the GraphQL generated types was incorrectly typed asstring, which may not accurately represent the actual data type returned by the API.WHAT is this pull request doing?
Changes the
updatedAtfield type fromstringtounknownin theDevSessionCreateMutationandDevSessionUpdateMutationGraphQL generated types. This provides more flexibility in handling the timestamp data without making assumptions about its format.How to test your changes?
updatedAtfield can be properly handled in consuming codeMeasuring impact
How do we know this change was effective? Please choose one:
Checklist