-
Notifications
You must be signed in to change notification settings - Fork 756
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
Replace the provider
keyword with the extension
keyword
#14379
Conversation
Test this change out locally with the following install scripts (Action run 9650842308) VSCode
Azure CLI
|
@@ -23,7 +23,7 @@ public class CentralizedProviderVersionManagementTests : TestBase | |||
public void ProvidersConfig_SupportForConfigManagedProviderDeclarationSyntax_When_ProviderIsBuiltIn(string providerIdentifier, bool shouldSucceed, (string code, DiagnosticLevel level, string message)[] expectedDiagnostics) | |||
{ | |||
var result = CompilationHelper.Compile(Services, @$" | |||
provider {providerIdentifier} | |||
extension {providerIdentifier} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you mentioned in the PR description, will providerIdentifier be changed in another PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this is tracked by #14375.
@rynowak fyi you already missed out on being able to use |
Good change 👍 The term |
/cc @shruthikumar |
As the first step of addressing #14374, this PR replaces the provider keyword with the extension keyword. Using the provider keyword will now trigger a warning diagnostic with a code fix to assist users in migrating to the new keyword.
To reduce the scope of this PR, the use of
provider
within the Bicep CLI, Bicep configuration, and the codebase will be replaced separately in subsequent PRs.Closes #14378.
Microsoft Reviewers: Open in CodeFlow