[vim/vim] runtime(bicep): treat bicepparam files as separate filetype (PR #19026)
Scott McKendry
Adds the bicep-params filetype to allow better bicep language support out of the box, adds two new ftplugin files for bicep and bicep-params.
Why two filetypes?
The bicep language server handles parameter files differently than regular bicep files. Treating them the same at the editor level leads to false positive diagnostics in the editor. To work around this, I've had my own ftplugin and ftdetcect configs for quite some time.
References
Bicep Language Constants:
https://github.com/Azure/bicep/blob/51392d32ca2c8b94b1bb7a255e78e1d559d12573/src/Bicep.Core/LanguageConstants.cs#L23
VS Code Extension definition:
https://github.com/Azure/bicep/blob/51392d32ca2c8b94b1bb7a255e78e1d559d12573/src/vscode-bicep/package.json#L47
You can view, comment on, or merge this pull request online at:
https://github.com/vim/vim/pull/19026
Commit Summary
- 5979e90 runtime(bicep): treat bicepparam files as separate filetype
File Changes
(4 files)
- M runtime/autoload/dist/ft.vim (2)
- A runtime/ftplugin/bicep-params.vim (3)
- A runtime/ftplugin/bicep.vim (14)
- M src/testdir/test_filetype.vim (3)
Patch Links:
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
chrisbra left a comment (vim/vim#19026)thanks. this is slightly backwards incompatible, but I hope it won't hurt that much, as bicep is probably not the most widely used language on the planet.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.
Christian Brabandt
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.