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.

Sign up for GitHub

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

Jump to bottom

Settings dialog #9316

Closed
aybiss opened this issue Mar 1, 2021 · 2 comments
Closed

Settings dialog #9316

aybiss opened this issue Mar 1, 2021 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@aybiss
Copy link

aybiss commented Mar 1, 2021

Description of the new feature/enhancement

Instead of spending time creating settings in json, documenting settings, fielding bug reports from people who can't find settings in json, and describing how to use the settings in json, how about creating the json file ONCE in entirety, and (optional) using it to create a settings dialog?

Proposed technical implementation details (optional)

  1. Instead of shipping a json file with like 2 out of the hundreds of options and then spending time documenting the possible options and values, put all the options in the json with descriptions of the values.

  2. Having created the json, second phase is to use it for populating a settings dialog in the program.
@aybiss aybiss added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 1, 2021
@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 Mar 1, 2021
@zadjii-msft
Copy link
Member

Please search before filing new issues.

/dup #1564
/dup #6800

@ghost
Copy link

ghost commented Mar 1, 2021

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Mar 1, 2021
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Mar 1, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @aybiss