Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include widget info in JSON Schema produced by @types endpoint #104

Closed
lukasgraf opened this issue May 20, 2016 · 4 comments
Closed

Include widget info in JSON Schema produced by @types endpoint #104

lukasgraf opened this issue May 20, 2016 · 4 comments

Comments

@lukasgraf
Copy link
Member

The JSON Schema produced by @types/[portal_type] currently only includes the field type, but no information about which widget should be used. This information should be included in the JSON Schema as well.

A custom widget for a field can be specified using a plone.autoform directive. That information then gets stored on the schema interface using tagged values, which should be easy to access and serialize.

The default widget however for a particular zope.schema field type is currently being determined by z3c.form, which means we might need to replicate some of z3c.form's logic.

/cc @ebrehault

@lukasgraf lukasgraf added this to the Future milestone May 20, 2016
@tisto
Copy link
Member

tisto commented Feb 17, 2017

We need this as well soonish. We already include a widget attribute for some fields but not for all. Will look into it.

@ebrehault
Copy link
Member

In angular2-schema-form, we use a widget property which is either a string (the id of the widget), either a dictionary if we need widget settings (like for a date/time, tinymce, etc.). See
https://github.com/makinacorpus/angular2-schema-form#widgets

@tisto tisto modified the milestones: Future, BeethovenSprint2017 Feb 17, 2017
@tisto
Copy link
Member

tisto commented Feb 17, 2017

@ebrehault using the widget property is fine. I just would make sure the property is always included and not "None" as it is now.

@tisto
Copy link
Member

tisto commented Feb 21, 2017

Pull request: #205

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants