lusaxweb / vuenut Goto Github PK

You have in the official website [https://lusaxweb.github.io/vuenut.org/] this issue.

The method consultarFunctions from the component myFunctions.vue, is not taking care about the posibility that the item recovered from the localStorage could be empty.

Translated to Spanish:

En el sitio oficial [https://lusaxweb.github.io/vuenut.org/] tiene el caso de reproducción.

Al parecer en el componente myFunctions.vue en el método consultarFunctions, no se está controlando la posibilidad de que el valor recuperado del localStorage sea vacío.

If we remove the entire value of an entry from the jsonview, and it misses the focus (clicking another entry in the jsonview), we are not able to set a value in that entry anymore.

Null value should be treated as another value after all.

Hello,

The npm published versions of vuenut should not print their own debug info into console.log as it adds noise and obstructs the user's debugging (and it's commonly in debugging that I use Vuenut anyway). At least hide the console output behind a runtime flag that can be given to vuenut when instantiating it e.g. Vue.use(vuenut, { debug: true }).

First off, an amazing tool! This really is a very minor issue.
I want to assign this to myself, but just posting as an issue to see if people agree?
I could make these changes in the css, as I've done in dev tools just experimentally.

Currently the icons are difficult to see in 'night mode'.

Above is my proposed change with new icon color as white for higher contrast, and better accessibility.

If an entry in our state has null as value, we reach this error:
TypeError: Cannot convert undefined or null to object

Hi,
This component is interesting.

You should translate title icons in english : copiar, guardar, cambiar formato for examples

If you want, i can do pull request

In my personal case there is a namespace where I hold references to instances of some classes that are related to libraries that are DOM-bound, and very complex with a lot of methods, circular references etc.

In general these references cause me no grief and work as they should, but I've started toying with your library and noticed that these references break Vuenut,

The easiest solution for me would be to ignore the entire namespace in Vuenut.

You should add a prop where user gives you a lists of strings with namespaces or store state objects to be ignored, even better if you had some way to denote paths like state.namespace.object or state.object.subobject could be given as :ignore=['namespace/object', 'object/subobject'] and Vuenut would just not add these to the "exploration tree".