You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With a previous version I was able to open a json editor and paste in json for viewing without specifying a file name. This was really useful for reviewing json output from a log. I got formatting and coloring and so on. Now, it seems I have to specify a file name, which slows me down and clutters my file system since I have no need to persist this temporary data. I have to specify the json editor and then I also have to specify a json extension in the file name; otherwise, I just get a texxt editor. This workflow has gotten significantly more complicated. I'd prefer to go back to being able to defer specifying a file name until I decide that I want to save the data. This is the way it works when opening a new text file. Consistency in the new file workflows would be good. I don't know if the change in workflow was intentional/by-design or not, but for me this has been a regression.
The text was updated successfully, but these errors were encountered:
With a previous version I was able to open a json editor and paste in json for viewing without specifying a file name. This was really useful for reviewing json output from a log. I got formatting and coloring and so on. Now, it seems I have to specify a file name, which slows me down and clutters my file system since I have no need to persist this temporary data. I have to specify the json editor and then I also have to specify a json extension in the file name; otherwise, I just get a texxt editor. This workflow has gotten significantly more complicated. I'd prefer to go back to being able to defer specifying a file name until I decide that I want to save the data. This is the way it works when opening a new text file. Consistency in the new file workflows would be good. I don't know if the change in workflow was intentional/by-design or not, but for me this has been a regression.
The text was updated successfully, but these errors were encountered: