Add ability to configure atomic saving #13656
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a problem hiding this comment.
This shouldn't be configurable via EditorConfig since it isn't a standard key.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some file watching/hot reloading programs, the way that Helix writes files can confuse them and cause them to throw errors or corrupt their caches. One such program is the
parcelbundlerhttps://parceljs.org/features/development/#known-issues-with-file-watching
They explicitly document that if your editor saves files using an "atomic save" or "safe write" or "backup copy" strategy, that it should be disabled. Helix currently does not allow you to disable this functionality, and adding this configuration option makes it so that that is possible.