Schema editor integration

[roll]

Control flow

• we listen for #field-schema[-url]/[-json] changes
• on changes we render tableschemaUI.EditorSchema with url/File/text as descriptor and onSave callback
• user do her schema edits
• on tableschemaUI.EditorSchema save click the component calls onSave(descriptor)
• we set descriptor to #field-schema value

Related

• Initial implementation focused on CKAN integration tableschema-ui#2
• https://github.com/okfn/docker-ckan-unhcr/pull/6
• Schema editor integration #25

[coveralls]

Coverage decreased (-0.2%) to 85.449% when pulling e70cfd4 on validation-schema into ed1c692 on master.

[coveralls]

Coverage decreased (-0.2%) to 85.449% when pulling e70cfd4 on validation-schema into ed1c692 on master.

[coveralls]

Coverage decreased (-0.2%) to 85.892% when pulling 78710ae on validation-schema into 9ce634a on master.

[roll]

@amercader
To run ckan with schema editor:

• checkout docker-ckan-unhcr/pull/6
• docker-compose -f docker-compose.val.yml up

[roll]

Known issues

• Click on X to close the modal doesn't work (does ckan has bootstrap scripts loaded?)
• Button Edit position is weird when we are changing schema via file/link/json -> Don't show Edit button when you click on other options #32
• Scripts/styles should be moved to proper places -> Move schema creator assets to fanstatic #30

[roll]

@amercader
Can you please review?

I've made the user control flow changes we've discussed (an issue for the schema editing - #34). A few things which are not resolved (please help if you can):

• allow schema editing/ensuring resource editing works OK (Allow to edit table schema using CKAN Schema Creator #34)
• moving schema buttons/inputs straight below the file button/inputs?
• fixing tests for ckan@2.4/2.5 (not sure how the failures in the builds related to this changes)

[roll]

@amercader
Can you please take a look how it works now?

TBH I feel like I'm missing something regarding your comment here - #34 (comment). And because of the bad sound quality haven't got fully your explanation during our call.

Of course, I'm pretty neutral on enabling/disabling the linked schema editing - just curious why the user can't edit the linked schema based on the same approach we have for the create resource page.

[roll]

@amercader
Are you able to remember what's this?)) I can't)

Have we integrated it already?