Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Change workspace configuration behavior
See original GitHub issueNow, if you define some icons in your workspace configuration it will override the user configuration, so you will end up losing all the customizations you have.
Ideally, the workspace configuration should be merged to the user configuration. It seems that vscode.workspace.getConfiguration method does the overriding so the only way to overcome this is to provide a slighty different syntax in the workspace.
The idea is to keep backwards compatibility so the current behavior will be kept and people will not lose what they already have but also to provide this new syntax that will allow to keep both workspace and user customizations.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:16 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@ciel never mind, I meant
asking for. I’m not an English native so I often forget the subtleties of the language.@robertohuertasm I just had an epiphany. How about adding a setting (user level) where the user can set a path to the custom icon folder? This way the user could also point to a cloud service folder.