You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #25 the user is able to infer a schema based on the provided data file:
Step 1
After uploading the file we show Infer
Step 2
After clicking on the Infer above (a modal window)
Step 3
After clicking on the Save above
Improvements
But we'd like to provide also an ability to edit already loaded/inferred schema. UI could be like this (an Edit button could be something like Open Editor etc):
After a click on the Edit button we back to the scenario above starting from the Step 2.
The tableschemaUI.EditorSchema fully supports stand-alone schema editing we just need to provide schema as a part of props instead of source as we do for the inferring.
Tasks
implement the described improvements
ensure that resource editing works as expected
The text was updated successfully, but these errors were encountered:
This all sounds brilliant @roll. The only thing I'm not sure about is the last bit about allowing to edit a linked schema. Right now the extension does not store remote schemas to allow these to be maintained separately. If users want to edit it they can download it and upload it.
Current
After #25 the user is able to infer a schema based on the provided data file:
Step 1
Step 2
Step 3
Improvements
But we'd like to provide also an ability to edit already loaded/inferred schema. UI could be like this (an
Edit
button could be something likeOpen Editor
etc):After a click on the
Edit
button we back to the scenario above starting from the Step 2.The
tableschemaUI.EditorSchema
fully supports stand-alone schema editing we just need to provideschema
as a part of props instead ofsource
as we do for the inferring.Tasks
The text was updated successfully, but these errors were encountered: