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
Because the activation event of the extension is set to onLanguage:sql we can't simply use this extension with other SQL languages (like PL/SQL). With a file that is using the PLSQL language mode when we execute the Format Document command it says that no formatter supporting this language is installed.
As a workaround we have to change the language of the file to SQL then format the document and finally set the document's language back to PLSQL.
That would be better to add multiple values to the onLanguage activation event so VS Code can recognize this extension as a valid formatter for other SQL flavors.
Note: it doesn't change anything that we set "sql-formatter.dialect":"pl/sql" in the settings or even "[plsql]":"editor.defaultFormatter": "adpyke.vscode-sql-formatter" }
The text was updated successfully, but these errors were encountered:
Because the activation event of the extension is set to
onLanguage:sql
we can't simply use this extension with other SQL languages (like PL/SQL). With a file that is using thePLSQL
language mode when we execute theFormat Document
command it says that no formatter supporting this language is installed.As a workaround we have to change the language of the file to
SQL
then format the document and finally set the document's language back to PLSQL.That would be better to add multiple values to the
onLanguage
activation event so VS Code can recognize this extension as a valid formatter for other SQL flavors.Note: it doesn't change anything that we set
"sql-formatter.dialect":"pl/sql"
in the settings or even"[plsql]":"editor.defaultFormatter": "adpyke.vscode-sql-formatter" }
The text was updated successfully, but these errors were encountered: