xyc / react-object-inspector Goto Github PK

Embedding this library in 0.1.x in a project with a modern build step was very easy and provided an opportunity to adjust and/or overwrite styles.

For example, I would like to use a different font-size and font-family. I don't think the library should be hard-coded with those sorts of decisions already made and set in stone.

For now I need to use !important rules but hope you consider an disableStyles or similar option and add relevant classNames back to nodes in the tree to facilitate 3rd party theming.

Cheers, great module!

I would like to be able to specify the collapsed / expanded state of the component:

a) expand a specific path "object.foo.bar"

b) expand noes down to a specific level number - ex: level 1 expands "object.keys" and level 2 expands "object.keys.keys"

Would also be nice to be able to override the label for the root node.

Babel 6.5.2

Module build failed: ReferenceError: [BABEL] ...node_modules/react-object-inspector/lib/ObjectInspector.js: Unknown option: ...node_modules/react-object-inspector/.babelrc.stage

react-object-inspector/.babelrc

{
  "stage": 0
}

I am using babel and for some reason the arrow character isn't rendering correctly...

Could it be babel?

Hi xyc

Currently, the gh-pages folder stands at 4.9mb, and is specially problematic for desktop applications made with electron-shell since it adds 4.9mb to each download.

Can it be excluded from the npm package?

just for FYI -
I am using it in - Check demo - http://nsisodiya.github.io/react-json-viewer/

Hey xyc

Really great work!

I just wanted to know what you think about adding support for inspection of proprties like __proto__, just the way it does in chrome dev tools?

The undefined value is rendered as Object.

Attached shot is from demo page:

Hi,

I would like to know if it's possible to show a "preview" of the node's content when this node is collapsed (like the first image on the README). It seems like this was the old behavior and that now , it has been changed.

It would be awesome if we had the choice between the two behaviors.

Thanks

Currently, all objects are displayed as Object, regardless of their prototype, unlike in DevTools.

The peer dependency of "react": "^0.14.0" conflicts with our project, since we use a newer version of react. The object inspector still works great with newer versions of React, so could you please update to a newer version of react or change the peer dependency to "react": "^0.14.0 || ^15.0.0",

Hi @xyc this module really helps! I'm wondering if you are thinking about move the css inline so that I can just install and use it!

Including an additional css is not hard but it would be cool if I don't need to do it at all!