Repository navigation
feat(gql-status-object): Introduce GqlNotification - #1641
Merged
Merged
Conversation
injectives
force-pushed
the
gql-status-object
branch
from
April 25, 2025 22:12
b9f0eeb to
3de51d7
Compare
injectives
marked this pull request as draft
April 25, 2025 22:13
injectives
force-pushed
the
gql-status-object
branch
3 times, most recently
from
April 25, 2025 22:28
709794d to
8123f76
Compare
injectives
changed the title
injectives
force-pushed
the
gql-status-object
branch
3 times, most recently
from
April 26, 2025 13:31
bfe055e to
bd199af
Compare
injectives
marked this pull request as ready for review
April 28, 2025 07:43
michael-simons
approved these changes
May 1, 2025
injectives
force-pushed
the
gql-status-object
branch
2 times, most recently
from
July 3, 2025 10:10
0553149 to
cae0c28
Compare
AndyHeap-NeoTech
approved these changes
Jul 3, 2025
BREAKING CHANGE: this update separates the new GQL Status Object hierarchy from the legacy `Notification` type by introducing a new `GqlNotification` interface that extends the `GqlStatusObject`. The update is based on the feedback received on the GQL Status Object feature, which is currently in preview. This should make it easier to understand the new GQL Status Objects and migrate from using the legacy `Notification` to the new types. Eventually, the new hierarchy is expected to replace the legacy `Notification` that is expected to be deprecated and phased out at a later date.
injectives
force-pushed
the
gql-status-object
branch
from
July 3, 2025 14:46
b65dbc1 to
f0eb7b7
Compare
AndyHeap-NeoTech
approved these changes
Jul 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
3 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.
BREAKING CHANGE: this update separates the new GQL Status Object hierarchy from the legacy
Notificationtype by introducing a newGqlNotificationinterface that extends theGqlStatusObject.The update is based on the feedback received on the GQL Status Object feature, which is currently in preview. This should make it easier to understand the new GQL Status Objects and migrate from using the legacy
Notificationto the new types.Eventually, the new hierarchy is expected to replace the legacy
Notificationthat is expected to be deprecated and phased out at a later date.