-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
json settings editor #794
Comments
Damn! I've really thought that the split had removed few months back!! I just found that it's option to check. No wonder that I will have to understand why it has been deprecated and removed in the first place. In the meantimes, you are welcome to make a PR. |
The old split JSON settings editor is more useful because when searching, the unmatched properties are hidden. I think the split JSON settings editor should be the default, like 2-3 years ago. The GUI isn't very useful... I've read the post, no real information about the tech limitation... |
You might want to upvote this issue (not sure it will make any difference but we can try): microsoft/vscode#129594 |
Here the patch to add back the previous JSON settings editor: json-settings-editor.patch.zip I've just copied the old version from |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment, and we'll keep it open. If you have any new additional information, please include it with your comment! |
!stale |
To just access the JSON settings:
To write a extension and add some buttons, here are the
|
I don't think we will re-implement the JSON settings editor. It will take too much time. @Crystal-RainSlide It was when the JSON settings editor was a split editor between the current editor and the reference file with sync search and other.... |
😭 |
@lonix1 Ya... Sorry Me too, I'm sad. |
hmmm (*2) This one don't seems like started though
|
With microsoft completely ignoring the voices of the community (shocking, right?), is there any chance you guys can revert that horrible bug they introduced?
microsoft/vscode#125952
The text was updated successfully, but these errors were encountered: