[BerislavLopac]

Does this use JSON Schema in any way? This looks like a perfect fit for it, much better than being "inspired by Typescript".

I particularly like the schema editor -- would it by any chance be available as a component to be used elsewhere, ideally open-source? I've been looking for a good browser-based editor for JSON Schema (or any schema, as long as it's configurable), but nothing I found really fits the bill.

[fdb75017]

Thanks for your feedback !

It does not rely on JSON schema at all, the idea was to build a representation that binds together data structure, views and behavior in a self-contained way (like .xlsx does).

There are a few tools that do enable to link JSON schema to views, like react-jsonschema-form (https://rjsf-team.github.io/react-jsonschema-form/) but you need to manage them separately, and they usually do not propose a way to add the fields "methods" (which was the feature I found interesting to make "dynamic" spreadsheets).

That being said, I think the framework should clearly propose an export from Schema to JSON Schema or Yaml at some point, just as you should be able to start building your Schema by importing a JSON Schema (and although there might be some gray zones between the 2).

No, sorry, it's not yet open-source, and currently there are some strong links between Document and Workspace (Links, Files...) that would need to be more "abstracted" to make the builder an independent component. But I hear you point ! (and all the comments in this thread are raising the same ! :) )

[BerislavLopac]

> There are a few tools that do enable to link JSON schema to views

I'm aware of those, but I'm looking for a visual way to declare JSON Schemas, similar to the Schema view in your project.

[fdb75017]

OK I see. I think exporting to JSON Schema is a feature to implement.

But again, there would be some situations where the 2 representations would not be reconcilable: you would not be able to stream out views & methods to JSON Schema, and in the other way, some weakly declared heterogeneous types of json schema like oneOf, allOf, anyOf might not always be representable in this framework.