[tsp-next] Replace use of visibility strings with Lifecycle visibility modifiers.#32952
Merged
witemple-msft merged 22 commits intoAzure:typespec-nextfrom Mar 3, 2025
Merged
Conversation
…tOptionality: false
…ted to satisfy lint rule
…sft/visibility-1_0-next
…sft/visibility-1_0-next
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
This was referenced Mar 3, 2025
Member
Author
|
Merging this to unblock others who are waiting on visibility changes. |
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
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.
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
@parameterVisibilitywith 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