-
Notifications
You must be signed in to change notification settings - Fork 753
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
Remove UserDefinedTypes feature flag #11461
Conversation
…-defined type syntax (or with symbolicNameCodegen enabled)
|
||
// malformed type but type check should still happen | ||
param malformedType2 44 = f | ||
//@[06:020) [no-unused-params (Warning)] Parameter "malformedType2" is declared but never used. (CodeDescription: bicep core(https://aka.ms/bicep/linter/no-unused-params)) |malformedType2| | ||
//@[21:023) [BCP283 (Error)] Using a literal value as a type requires enabling EXPERIMENTAL feature "UserDefinedTypes". (CodeDescription: none) |44| | ||
//@[26:027) [BCP057 (Error)] The name "f" does not exist in the current context. (CodeDescription: none) |f| |
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.
I was a bit surprised that this diagnostic hadn't been surfaced in the previous baseline version, but apparently param default values are not validated if there is an error encountered in the param type clause
src/Bicep.Cli/CliResources.resx
Outdated
@@ -147,4 +141,8 @@ | |||
<value>The specified input "{0}" was not recognized as a Bicep or Bicep Parameters file. Valid files must either the .bicep or .bicepparam extension.</value> | |||
<comment>{0} input file path</comment> | |||
</data> | |||
<data name="ExperimentalFeaturesDisclaimerMessage" xml:space="preserve"> | |||
<value>ntal Bicep features have been enabled: {0}. Experimental features should be enabled for testing purposes only. Do not enable these settings for any production usage, or you may be unexpectedly broken at any time!</value> |
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.
ntal
- typo!
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.
Resolves #4158 This PR also updates the TemplateWriter to target a non-experimental ARM languageVersion that allows type definitions (2.0). Templates using experimental ARM features (e.g., extensibility and asserts) now target the 2.1-experimental language version. The languageVersion change entailed a large number of baseline changes. These are included in this PR in a separate commit, and I'll go through and flag any unexpected baseline change. codeflow:open?pullrequest=#11461
Resolves #4158 This PR also updates the TemplateWriter to target a non-experimental ARM languageVersion that allows type definitions (2.0). Templates using experimental ARM features (e.g., extensibility and asserts) now target the 2.1-experimental language version. The languageVersion change entailed a large number of baseline changes. These are included in this PR in a separate commit, and I'll go through and flag any unexpected baseline change. codeflow:open?pullrequest=#11461
Resolves #4158
This PR also updates the TemplateWriter to target a non-experimental ARM languageVersion that allows type definitions (2.0). Templates using experimental ARM features (e.g., extensibility and asserts) now target the 2.1-experimental language version.
The languageVersion change entailed a large number of baseline changes. These are included in this PR in a separate commit, and I'll go through and flag any unexpected baseline change.
Microsoft Reviewers: codeflow:open?pullrequest=#11461