Skip to content

Comments

[tsp-next] Replace use of visibility strings with Lifecycle visibility modifiers.#32952

Merged
witemple-msft merged 22 commits intoAzure:typespec-nextfrom
witemple-msft:witemple-msft/visibility-1_0-next
Mar 3, 2025
Merged

[tsp-next] Replace use of visibility strings with Lifecycle visibility modifiers.#32952
witemple-msft merged 22 commits intoAzure:typespec-nextfrom
witemple-msft:witemple-msft/visibility-1_0-next

Conversation

@witemple-msft
Copy link
Member

This PR updates all specs to use Lifecycle visibility modifiers in place of stringly-typed visibilities. This is in accordance with the deprecation of stringly-typed visibilities in the next version of the TypeSpec core and removal in TypeSpec 1.0-rc.

It also deprecates use of @parameterVisibility with no arguments. The current behavior this causes was unintended, but nonetheless useful, so we now provide an explicit way to enable that behavior: @patch(#{ implicitOptionality: false }).

See: microsoft/typespec#6088

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Mar 3, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Mar 3, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@witemple-msft
Copy link
Member Author

Merging this to unblock others who are waiting on visibility changes.

@witemple-msft witemple-msft merged commit 3ed3dc3 into Azure:typespec-next Mar 3, 2025
16 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants