In version 0.10.2 I am having issues with making sure a file is saved with UTF-8 and BOM character encoding.
Please add such an option.
:+1:
I mean :+1: for having such an option, but :-1: for any tool that needs BOMs :)
@bpasero LOL, like powershell.
My strong position against BOMs is company agnostic ;)
.
I want to this feature too
:+1:
I really need this encoding type too. Is it planned in a future release?
need too :[
Having this capability would unblock PowerShell Script Analyzer identifying a Warning for new scripts authored using VSCode.
Pushed a change that allows to set a new setting files.bom to one of:
preserve (default): keep any existing UTF-8 BOM, but not add itinsert: always add a UTF-8 BOMremove: always remove any found UTF-8 BOM :+1:
Discussed with the team and we favor a different approach that does not include a new setting, instead we piggy back on the existing encoding option and add a new option UTF8 with BOM. This has several advantages:
UTF 8 with BOM or not by looking at the status bar encoding infoUTF 8 and UTF 8 with BOM by using the Save with Encoding action from the status bar picker and by picking UTF 8 to remove the BOM and the other to add itNow is better! you have to be able to save with BOM and save with BOM if the file already has it.
Most helpful comment
I mean :+1: for having such an option, but :-1: for any tool that needs BOMs :)