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

Attempt to heal settings files damaged by #9962 #10143

Merged
2 commits merged into from
May 21, 2021
Merged

Commits on May 20, 2021

  1. Attempt to heal settings files damaged by #9962

    The bug that caused #9962 resulted in folks getting profiles written to
    their settings that didn't contain any identifying information (name or
    guid), sometimes multiple times.
    
    These profiles look (somewhat) like this:
    
    ```json
    { "colorScheme": "Campbell" },
    {},
    ```
    
    An empty profile serves no purpose -- it shows up in the list as being
    named "Default", and it only launches CMD (unless the commandline is the
    thing that the user successfully changed.)
    
    We can heal the settings file by simply ignoring those profiles that
    have *no identifying information* (a guid or a name that can be
    converted into a guid).
    
    Validation
    ----------
    I created a number of profiles that fit this format and made sure that
    they were ignored on load and destroyed on save.
    DHowett committed May 20, 2021
    Configuration menu
    Copy the full SHA
    f86d28d View commit details
    Browse the repository at this point in the history
  2. don't do iterators bad

    DHowett committed May 20, 2021
    Configuration menu
    Copy the full SHA
    62553c7 View commit details
    Browse the repository at this point in the history