When dprint-vscode fails to find a configuration file, it does not register its formatting providers. This leads to a generic and misleading VS Code error message: 'Extension Dprint Code Formatter is configured as formatter but it cannot format -files'. This is false because dprint CAN format those files, it just doesn't have a config.\n\nIt would be better to show a more intelligent toast that explains no config was found and points the user to 'dprint init'.
When dprint-vscode fails to find a configuration file, it does not register its formatting providers. This leads to a generic and misleading VS Code error message: 'Extension Dprint Code Formatter is configured as formatter but it cannot format -files'. This is false because dprint CAN format those files, it just doesn't have a config.\n\nIt would be better to show a more intelligent toast that explains no config was found and points the user to 'dprint init'.