clearing of non-default schema properties

[kane-mason]

Expressa admin doesn't support all of the json-editor features, like description and default etc etc, which is fine but the problem is if you add them manually in the json, an update from the admin panel to the schema will clear all your manual updates, which is not nice :(

[thomas4019]

That does seem annoying. I've updated the schema editor to preserve the default value. Description should already be preserved because it's now supported by the schema editor, right?

[kane-mason]

ok yes the description does get preserved. two other properties that also get nuked are media and links

[thomas4019]

Fyi, I have a new JSON schema editor component written in Vue instead of React and should solve this issue. It's still not quite ready to be integrated yet though.

[thomas4019]

@kane-mason A demo of the new schema editor is available at https://www.thomashansen.me/json-schema-editor/

It is styled very similarly, but the implementation is very different and it should now preserve any keys that aren't understood. If you have time to try it out at that site, let me know if you run into anything.

[kane-mason]

@thomas4019 i had a bit of a play around with it and it seems to be good!

One bug i found is that if the required array is not present for each property of type: object then it throws an error.

Otherwise seems good, parsed my more complex schemas fine and seemed to retain custom properties.

Regarding the style, i think its good that its simple. But i think a creative person could really suggest some subtle styling that could make it more intuitive. Complex schemas can be very tricky to navigate! This is also true of json-editor

[kane-mason]

@thomas4019 any progress on this?

[thomas4019]

@kane-mason I ran into a blocking issue.
The expressa admin is bulit in Vue.
The expressa document editor uses json-editor
The old schema editor is built in React.

When I tried embedding the new schema editor as a json-editor plugin inside of the expressa Vue admin, I kept running into UI issues. Basically, UI updates wouldn't get triggered correctly which I think is due to Vue being embedded inside of Vue with another library in between.

[thomas4019]

Thinking about it now, I think I could avoid this issue and complexity, by not integrating the schema into json-editor but rather manually including it in the Expressa UI as a special case. I can try that out this week.