secondlife / secondlife/sl-vscode-plugin
Plugin needs to respond to config changes better
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 15
- Avg merge
- 14h 50m
- Merged PRs (30d)
- 9
Description
Several config flags when changed need to "enact" that change.
For instance on changing:
slVscodeEdit.storage.useLocalConfig- the plugin should regenerate the config in the new location
- And delete old?
slVscodeEdit.network.websocketPort- any active sockets should try reconnecting?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating where slVscodeEdit.storage.useLocalConfig and slVscodeEdit.network.websocketPort are handled, then clarify the expected behavior for config regeneration, old-config deletion, and active socket reconnection; done should be defined by tests for each change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100