You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vim plugin formats using stdin so that we can format without writing the buffer. We added --stdin-name argument so that error messages can include the file name and makes it easier for us to associate the errors back to the buffer. Now that formatting depends on language version can we add a --stdin-path argument to ask the formatter to treat the content as if it had been written to that location, and find the language version accordingly.
I've been thinking about it more and maybe it makes more sense to just use the existing --stdin-name option as the path and search for a package config surrounding that. If you don't want it to search, you can always disable that by passing in an explicit language version or --language-version=latest. What do you think?
If --stdin-name is given, then look for a surrounding package config to
infer the default language version from for code read from stdin. To
avoid that behavior, you can pass in a language version explicitly
using --language-version.
Fix#1530.
The vim plugin formats using stdin so that we can format without writing the buffer. We added
--stdin-name
argument so that error messages can include the file name and makes it easier for us to associate the errors back to the buffer. Now that formatting depends on language version can we add a--stdin-path
argument to ask the formatter to treat the content as if it had been written to that location, and find the language version accordingly.#1402 (comment)
The text was updated successfully, but these errors were encountered: