Recognize Bicep parameter files as text - #241
Merged
SimonCropp merged 1 commit intoSep 22, 2026
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Member
|
thanks. i will deploy this now |
This was referenced Sep 22, 2026
Merged
Merged
Merged
This was referenced Sep 24, 2026
Closed
Merged
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
2 participants
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.
Summary
Add
.bicepparamto the built-in text extensions alongside.bicep. Azure's official documentation identifies.bicepparamas the native Bicep parameter file extension.FileExtensions.IsTextExtension("bicepparam")andFileExtensions.IsTextFile("main.dev.bicepparam")now returntruewithout custom registration. Regression tests cover lowercase, uppercase, and mixed-case extensions, dotted and dotless lookups, and string/span overloads.Validation
ExtensionsTestscases pass on both .NET 8 and .NET 10.git diff --checkpasses.The pinned .NET 11 SDK was not installed locally. Targeted builds/tests used the installed .NET 10 SDK with process-only SDK resolver and target-framework overrides; repository SDK configuration is unchanged. The .NET 8 build emitted Polyfill's target-framework advisory for the narrowed validation target. Full .NET 11 validation was not run.