🐛 Extension doesn't work for New Files

[ZachHaber]

Environment information

Rome Extension: v0.12.0
No Rome CLI installed globally or locally,

VSCode Env Info:
Version: 1.69.2 (user setup)
Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a
Date: 2022-07-18T16:12:52.460Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 10.0.19044

What happened?

I don't have Rome installed separately from the extension.

1. In a project configured with Rome
2. Create a new file
3. Add code to the file and set the language to Typescript or JS
4. Attempt to format the file with Rome

The Rome Trace doesn't even see the attempt at running the formatter either.

Expected result

Rome should be able to format new files in VSCode. Even if that's the default because there's no approach to get access to the rome.json associated due to the lack of file paths.

Code of Conduct

• I agree to follow Rome's Code of Conduct

[ematipico]

It seems that our extension doesn't support formatting for newly created files:

Not sure if it's a bug or a feature, but surely it's something we would like to support

[leops]

Some technical information about this: at the moment the extension only activates on documents with the file:// scheme because we rely on the name of the file (and more specifically its extension) to determine the file type. In order to support files that do not have a path on disk yet, we'd need to provide an explicit file type to the workspace (probably derived from the language mode of the editor if we can access it over the LSP)