Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings file being reformatted when settings are changed by the program #2411

Closed
giggio opened this issue Aug 12, 2019 · 5 comments
Closed
Assignees
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Milestone

Comments

@giggio
Copy link

giggio commented Aug 12, 2019

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0                                                                                                                                                                                     

Windows Terminal version: latest from the master branch

Any other software?
N/A

Steps to reproduce

With the terminal closed, do anything that trigger a json settings file rewrite, for example, add any setting to the settings json file that is not on the schema (or is invalid), for example:

{
    "Foo": 1,
    "globals" :
    {

Then, open the terminal

Expected behavior

Terminal warns me somehow, or comments out the invalid setting. But does not, ever, reformat the file.

Actual behavior

The settings file is rewritten and reformatted, and, worse of all, an annoying trailing space is added to the end of every json key. See image bellow:

CodeSettingsFile

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 12, 2019
@DHowett-MSFT
Copy link
Contributor

Getting rid of this behavior is a critical (and already called out!) part of the work specified in #1258. 😄

@DHowett-MSFT DHowett-MSFT added Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 12, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 12, 2019
@DHowett-MSFT DHowett-MSFT added this to the Terminal v1.0 milestone Aug 12, 2019
@egmontkob
Copy link

The Actual vs. Expected behavior sections are swapped, aren't they?

@giggio
Copy link
Author

giggio commented Aug 13, 2019

Yes, fixed, thanks.

@DHowett-MSFT
Copy link
Contributor

@zadjii-msft got rid of settings reserialization recently. 😄

@ghost ghost added the Needs-Tag-Fix Doesn't match tag requirements label Aug 23, 2019
@DHowett-MSFT DHowett-MSFT added Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. and removed Needs-Tag-Fix Doesn't match tag requirements labels Aug 23, 2019
@giggio
Copy link
Author

giggio commented Aug 26, 2019

Awesome, I just confirmed it with my latest private build. Tks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

No branches or pull requests

4 participants