search

dfrnt-com / support

DFRNT.com support and documentation
https://support.dfrnt.tech
1 stars 0 forks source link

Moving properties in Edit Schema does not save #14

Open tech41 opened 1 year ago

tech41 commented 1 year ago

On the Edit Schema page for a type or trait, there are arrows to move a property up or down (which is a nice feature!). However after hitting Update, the properties revert back to their previous order.

hoijnet commented 1 year ago

The properties in TerminusDB are unordered and this is due to the component used in DFRNT to render the forms.

There is a workaround for the display of them in DFRNT with the SchemaClassMetadata type.

image

Create one with an ID of SchemaClassMetadata/ and set the propertyDisplayOrder. This will make the rendered documents show up correctly in DFRNT.

This came into existence before the Class Metadata was a thing and is considered as deprecated as I intend to move these into Metadata fields on the type.

The form doc editor, JSON and YAML do not follow this yet.

Hope it helps with the situation. I will update here once this changes.

hoijnet commented 1 year ago

It would be interesting to get some more background on the reasons for moving the properties up and down, and what the expectation is that it would change in DFRNT once moved.

tech41 commented 1 year ago

It's a minor point, basically just that some properties are logically grouped together and so it would be nice to be able to display them as such.

The reason I tagged it as an issue was that the property editor in DFRNT has arrows that can move the properties up and down. So I assumed that if I could move them in the property editor, the changes would persist. Like I said, it's pretty minor, but it seemed like an inconsistency.

hoijnet commented 1 year ago

I realized that there might actually a way to get this supported, and that this could be the UI for it. Thanks for raising the issue and exciting the imagination. The deprecated SchemaClassMetadata is moving into the metadata section of the class with the next release. Editing the field order still had a missing UI, and this could be a nice way to accomplish that.

Thanks for the idea! Let me think of how to implement it! Could actually be solved in a future release!