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
When updating my NPM packages in Visual Studio... for most packages I can link over to the repository to look for changes.
The link for vanilla-jsoneditor points to the homepage at https://jsoneditoronline.org/. But there's no link from the homepage over to the repository, so I usually get there through Google, which takes a little longer.
Thanks for bringing this up, that is indeed not handy. I utilized two fields in the package.json: one for the homepage where you see the library in action, and one for the source repository (see npm):
There is indeed not an easy to find link to the github repo from the website https://jsoneditoronline.org/. I'll see if I can improve on that one way or another.
I've change the homepage field to the Github repo. The Readme starts with the following section, so it will still be easy to try it out in the web application:
A web-based tool to view, edit, format, transform, and validate JSON.
When updating my NPM packages in Visual Studio... for most packages I can link over to the repository to look for changes.
The link for vanilla-jsoneditor points to the homepage at https://jsoneditoronline.org/. But there's no link from the homepage over to the repository, so I usually get there through Google, which takes a little longer.
An improvement might be to have a link to the git repo(s) from the homepage at https://jsoneditoronline.org/.
The text was updated successfully, but these errors were encountered: