json-edit-react 0.9.0 → 0.9.1

package/README.md

@@ -31,6 +31,7 @@ Features include:
 - [Undo functionality](#undo-functionality)
 - [Issues, bugs, suggestions?](#issues-bugs-suggestions)
 - [Roadmap](#roadmap)
+- [Inspiration](#inspiration)
 - [Changelog](#changelog)
 
 
@@ -215,7 +216,7 @@ However, you can pass in your own theme object, or part thereof. The theme struc
 
 ```
 
-The `styles` property is the main one to focus on. Each key (`property`, `bracket`, `itemCount`) refers to a part of the UI. The value for each key is *either* a `string`, in which case it is interpreted as the colour (or background colour in the case of `container` and `inputHighlight`), *or* a full CSS style object for fine-grained definition. You only need to provide properties you wish to override —— all unspecified ones will fallback to either the default theme, or another theme that you specify as the "base".
+The `styles` property is the main one to focus on. Each key (`property`, `bracket`, `itemCount`) refers to a part of the UI. The value for each key is *either* a `string`, in which case it is interpreted as the colour (or background colour in the case of `container` and `inputHighlight`), *or* a full CSS style object for fine-grained definition. You only need to provide properties you wish to override — all unspecified ones will fallback to either the default theme, or another theme that you specify as the "base".
 
 For example, if you want to use the "githubDark" theme, but just change a couple of small things, you'd specify something like this:
 
@@ -328,7 +329,12 @@ The main features I'd like to introduce are:
 2. **Visibility filter function** — *hide* properties from the UI completely based on a Filter function. This should arguably be done outside the component though (filter the data upstream), so would be less of a priority (though it would be fairly simple to implement, so 🤷‍♂️)
 3. **Search** — allow the user to narrow the list of visible keys with a simple search input. This would be useful for very large data objects, but is possibly getting a bit too much in terms of opinionated UI, so would need to ensure it can be styled easily. Perhaps it would be better if the "Search" input was handled outside this package, and we just accepted a "search" string prop?
 
+## Inspiration
+
+This component is heavily inspired by [react-json-view](https://github.com/mac-s-g/react-json-view), a great package that I've used in my own projects. However, it seems to have been abandoned now, and requires a few critical fixes, so I decided to create my own from scratch and extend the functionality while I was at it.
 
 ## Changelog
 
-- **0.9.0**: Initial release
+- **0.9.0**: Initial release
+- **0.9.1**: Export more Types from the package
+

package/build/index.d.ts

@@ -95,4 +95,4 @@ type CompareFunction = (a: string, b: string) => number;
 
 declare const JsonEditor: React$1.FC<JsonEditorProps>;
 
-export { JsonEditor, Theme, ThemeName, themes };
+export { JsonEditor, Theme, ThemeInput, ThemeName, themes };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "json-edit-react",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "React component for editing or viewing JSON/object data",
   "main": "build/index.cjs.js",
   "module": "build/index.esm.js",