Enforce .bicep extension on Bicep build command #6609
Merged
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.
Fixes #1369
Fixes #5091
This PR allows
bicep build
to exit early with a meaningful error message when a non-bicep file is provided as the command's entry point. It does so by enforcing that bicep files use the.bicep
extension (per the discussions in #5091 and in #1369 (comment)) by adding a newAuxiliaryTextFile
subtype ofISourceFile
to use for any file that is not a JSON ARM template or file with the.bicep
extension. This source file type has a corresponding empty semantic model.This is a breaking change, and it might make sense to bundle this with other breaking changes in a release with a meaningful version number bump. I did have to modify a number of tests that were creating bicep files without the correct extension, and I suspect many users who are synthesizing bicep files and then invoking the compiler may need to do the same.
Contributing a feature