johnpapa/vscode-peacock

Peacock without a workspace: Allow option for colors to only affect one user and one instance

Open

#7 opened on Feb 22, 2019

View on GitHubContributor guide
 (79 comments) (204 reactions) (0 assignees)TypeScript (151 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (1,174 stars)
PR merge metrics
 (Avg merge 15d 20h) (27 merged PRs in 30d)

Description

Currently the extension sets the colors in workspace settings. THis means whatever settings are in that file are then either gitignored or allowed, and then team members will also get your color. It may be desirable for many to only let the color affect one instance of vscode and for a specific user.

Contributor guide

Research direction
Investigate how Peacock currently sets workspace settings via VS Code's workspace configuration. Explore using user level settings (GlobalState or setting scope 'application') to restrict color changes to a single user or VS Code instance. Implement a configuration option to choose between workspace and user/instance scope.
Tech stack
typescript
Domain
frontenddeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Visual Studio Code extension developmentTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65