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

Allow more settings to be global, not per profile #3098

Closed
Stanzilla opened this issue Oct 6, 2019 · 2 comments
Closed

Allow more settings to be global, not per profile #3098

Stanzilla opened this issue Oct 6, 2019 · 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

@Stanzilla
Copy link
Contributor

Description of the new feature/enhancement

Currently it is not possible to set colorScheme or padding on a global level, only per profile.

Proposed technical implementation details (optional)

Every setting that can be per-profile, minus the obvious ones like name and guid etc, should be able to be set on a global level as well.
@Stanzilla Stanzilla added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 6, 2019
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 6, 2019
@DHowett-MSFT
Copy link
Contributor

This'll be addressed by /dup #2325. Thanks!

@ghost
Copy link

ghost commented Oct 6, 2019

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 Oct 6, 2019
@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 Oct 6, 2019
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
@Stanzilla @DHowett-MSFT