Revisit the use of `ITextEditorService` in preferences component
See original GitHub issueWe want to move away from allowing anyone to create heavy typed editor inputs. One clear method we need to deprecate is IEditorService.createEditorInput
. The usages we have today need to be changed to untyped inputs.
We seem to be having a few places left:
Preferences @roblourens
Custom Editors
Text Editors
We then have quite a few more usages that imho are less critical because they originate from contexts where we actually do want typed inputs (editor input deserialisation). However, we should probably move those into respective components and out of the editor service itself. I will create a follow up issue on that.
Issue Analytics
- State:
- Created 2 years ago
- Comments:21 (21 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Settings editor is the last remaining one.
Will be deleted first thing in debt week when I get rid of the split json editor 😁