- fix: dispose formatting edit provider on config reinitialization (#141)
- fix: instead of focusing output window on error, show notification (#140)
- fix: update do not allow to deny (#130)
- fix: fallback to global dprint when disallowing workspace
"dprint.path"config (#128)
- feat: prompt for custom workspace
"dprint.path"setting (#126) - Revert "fix: improve how dprint executable is launched (#121)" (#125)
Adds a security measure to prompt when someone provides a custom "dprint.path" vscode workspace setting so that this extension doesn't launch a workspace defined executable on startup without explicit user approval.
- fix: improve how dprint executable is launched (#121)
- fix: improve config discovery (#111)
- fix: retry trying to find config files with vscode API if one found in root with fs api (#109)
- fix: wait for workspace to be initialized before checking for configuration files (#106)
- fix: prevent logger debug output loss (#103)
- perf: avoid calling process.report.getReport() on startup (#99)
- fix(npm): run dprint from a temp directory on Windows (#92)
- fix: ensure duplicate processes don't appear when restarting or changing config (#85)
- fix: initialize backend only if configuration file exists (#80)
- feat: add
dprint.experimentalLsp
- fix: exclude searching for dprint config files in node_modules folders
- feat: auto-discover dprint in ancestor node_modules directories (#66)
- feat: rename dprint.reset to dprint.restart (#65)
- perf: lazily startup editor process (#64)
- feat: auto-discover dprint.jsonc config (supported in dprint 0.36+)
- fix: focus the dprint output window max one time per session
- fix: regression opening a descendant directory of a folder with a config file
- perf: reduce startup cpu usage with multiple workspace folders
- fix: regression where dprint versions <= 0.28 stopped formatting
- fix: ensure large files get formatted on Mac
- fix: handle dprint process being killed by an outside force
- feat: expand
~/in the dprint.path configuration to the home directory
- fix: support folders with spaces when resolving node_modules path and in
"dprint.path"configuration
- feat: prefer resolving dprint executable in node_modules
- feat: support for editor schema v5 (#30)
- Support sub directories with dprint configuration files.
- Support multiple workspace folders.
- Do not show notification for formatting errors (it only outputs to the output tab).
- Better handling when default schema can't be downloaded.
- Extension is bundled to single JS file to improve load times.
- Support config files in ancestor directories of the workspace.
- Support for dprint 0.17
- Get config file schema from plugins.
- Add logging to "output" tab in vscode (under "dprint").
- Add
"dprint.verbose"config for outputting verbose logging.
- Support dprint 0.13
- Support dprint 0.12
- Add "dprint.path" setting.
- Update to work with dprint 0.10.0 (will be backwards compatible with 0.9.0 for now).
- Plugin now re-initializes when the configuration file changes.
Fix format error message displaying (was [object Object] or whatever instead of a string).
Formatting is faster due to using a long-running background process for formatting.
- Instructional message when dprint is not installed globally.
- Fix encoding issue on error.
Updates based on latest dprint CLI.
Fix error text.
Auto-dismiss syntax error notifications.
Initial release.