Skip to content

Deprecation changes are incorrectly formatted on schema version view #6692

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

Open
n1ru4l opened this issue Apr 2, 2025 · 0 comments
Open

Deprecation changes are incorrectly formatted on schema version view #6692

n1ru4l opened this issue Apr 2, 2025 · 0 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@n1ru4l
Copy link
Contributor

n1ru4l commented Apr 2, 2025

SDL:

enum CriticalityLevel {
  Breaking
    @deprecated(
      reason: "Use 'SeverityLevelType' instead. This field will be removed once it is no longer in use by a client."
    )
  Dangerous
    @deprecated(
      reason: "Use 'SeverityLevelType' instead. This field will be removed once it is no longer in use by a client."
    )
  Safe
    @deprecated(
      reason: "Use 'SeverityLevelType' instead. This field will be removed once it is no longer in use by a client."
    )
}

Rendered UI:

Image

The word Use is in a code block, the actual message is not. Thsi si probably related to the usage of ' within the deprecation message.

Example on staging: https://app.staging.graphql-hive.com/the-guild/graphql-hive/staging/history/c4bd48a7-5bbc-493b-9d8a-eb6848894479

@n1ru4l n1ru4l added help wanted Extra attention is needed good first issue Good for newcomers labels Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Development

No branches or pull requests

1 participant