Format enum deprecation messages #3983
Assignees
Labels
area/api-docs
Generated API docs, generated from providers. For hand-written docs, see area/docs.
kind/bug
Some behavior is incorrect or out of spec
kind/enhancement
Improvements or new features
resolution/fixed
This issue was fixed
size/S
Estimated effort to complete (1-2 days).
Milestone
Comments
sean1588
added
kind/enhancement
github-merge-queue bot
pushed a commit
to pulumi/pulumi
that referenced
this issue
Feb 27, 2024
fixes: pulumi/registry#3983 This PR fixes up some issues with our deprecation message formatting. The deprecation messages attached to enums were not being formatted at all, due to a missing css class. Secondly, I also noticed there was a whitespace missing in the deprecation message when it renders in the browser, due to the leading `-` in `{{- .... -}}`, so I addressed that here as well. ### enum deprecation before:  after:  ### fix whitespace after "Deprecated:" before:  after: 
github-merge-queue bot
pushed a commit
to pulumi/pulumi
that referenced
this issue
Feb 27, 2024
fixes: pulumi/registry#3983 This PR fixes up some issues with our deprecation message formatting. The deprecation messages attached to enums were not being formatted at all, due to a missing css class. Secondly, I also noticed there was a whitespace missing in the deprecation message when it renders in the browser, due to the leading `-` in `{{- .... -}}`, so I addressed that here as well. ### enum deprecation before:  after:  ### fix whitespace after "Deprecated:" before:  after: 
github-merge-queue bot
pushed a commit
to pulumi/pulumi
that referenced
this issue
Feb 27, 2024
fixes: pulumi/registry#3983 This PR fixes up some issues with our deprecation message formatting. The deprecation messages attached to enums were not being formatted at all, due to a missing css class. Secondly, I also noticed there was a whitespace missing in the deprecation message when it renders in the browser, due to the leading `-` in `{{- .... -}}`, so I addressed that here as well. ### enum deprecation before:  after:  ### fix whitespace after "Deprecated:" before:  after: 
github-merge-queue bot
pushed a commit
to pulumi/pulumi
that referenced
this issue
Feb 28, 2024
fixes: pulumi/registry#3983 This PR fixes up some issues with our deprecation message formatting. The deprecation messages attached to enums were not being formatted at all, due to a missing css class. Secondly, I also noticed there was a whitespace missing in the deprecation message when it renders in the browser, due to the leading `-` in `{{- .... -}}`, so I addressed that here as well. ### enum deprecation before:  after:  ### fix whitespace after "Deprecated:" before:  after: 
github-merge-queue bot
pushed a commit
to pulumi/pulumi
that referenced
this issue
Mar 2, 2024
fixes: pulumi/registry#3983 This PR fixes up some issues with our deprecation message formatting. The deprecation messages attached to enums were not being formatted at all, due to a missing css class. Secondly, I also noticed there was a whitespace missing in the deprecation message when it renders in the browser, due to the leading `-` in `{{- .... -}}`, so I addressed that here as well. ### enum deprecation before:  after:  ### fix whitespace after "Deprecated:" before:  after: 
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that enums are able to be rendered on the page, it's apparent we are not handling the deprecation message formatting the way we do for properties. We should match the formatting we use for deprecated properties.
The text was updated successfully, but these errors were encountered: