Skip to content
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.

Sign up for GitHub

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

docs: update/annotate formerly experimental configs #5938

Merged
merged 3 commits into from
Sep 4, 2024
Merged

docs: update/annotate formerly experimental configs #5938

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ac2bdb1
Update experimental configs
Meschreiber Sep 3, 2024
761c226
Address suggestions
Meschreiber Sep 4, 2024
b60da26
Merge branch 'dev' into docs/update-experimental-configs
Meschreiber Sep 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions docs/source/configuration/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -598,9 +598,13 @@ supergraph:

</MinVersion>

<ExperimentalFeature />
<Note>

Beginning with [v1.49.0](https://github.com/apollographql/router/releases/tag/v1.49.0), the router supported enhanced operation signature normalization [experimentally](/resources/product-launch-stages/#experimental-features).
In [v.1.53.0](https://github.com/apollographql/router/releases/tag/v1.53.0), this configuration became [generally available](/resources/product-launch-stages/#general-availability).
Meschreiber marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The config rename will happen in v1.54.0, so we should use that as the version it became GA (and not merge this until then).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is merging into dev, so I think we can/should merge before the release, right?

Copy link
Member

@abernix abernix Sep 4, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! We'll start 1.54.0 (as a release candidate) today and this will not land in our docs until next Tuesday when we finalize 1.54.0. 😄 I'll merge this to make sure it makes the cut. (It looks like the version was already raised to 1.54.0 in the text, which is totes right.)


</Note>

Beginning in v1.49.0, the router supports enhanced operation signature normalization.
Apollo's legacy operation signature algorithm removes information about certain fields, such as input objects and aliases.
This removal means some operations may have the same normalized signature though they are distinct operations.

Expand Down Expand Up @@ -761,11 +765,17 @@ query AliasedQuery {

</MinVersion>

<ExperimentalFeature />
<Note>

Beginning with [v1.50.0](https://github.com/apollographql/router/releases/tag/v1.50.0), the router supported extended reference reporting [experimentally](/resources/product-launch-stages/#experimental-features).
In [v.1.53.0](https://github.com/apollographql/router/releases/tag/v1.53.0), this configuration became [generally available](/resources/product-launch-stages/#general-availability).
Meschreiber marked this conversation as resolved.
Show resolved Hide resolved

</Note>


<EnterpriseFeature linkWithAnchor="https://www.apollographql.com/pricing#graphos-router" />

Beginning in v1.50.0, you can configure the router to report enum and input object references for enhanced insights and operation checks.
You can configure the router to report enum and input object references for enhanced insights and operation checks.
Apollo's legacy reference reporting doesn't include data about enum values and input object fields, meaning you can't view enum and input object field usage in GraphOS Studio.
Legacy reporting can also cause [inaccurate operation checks](#enhanced-operation-checks).

Expand Down
Loading