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

Allow for more dynamic extension customisation by user #181

Closed
lukasoppermann opened this issue Jan 2, 2019 · 3 comments
Closed

Allow for more dynamic extension customisation by user #181

lukasoppermann opened this issue Jan 2, 2019 · 3 comments

Comments

@lukasoppermann
Copy link

Hey, it would be neat if the user could customise extensions more (easily).

For example if you have an editor for objects like https://github.com/lukasoppermann/contentful-key-value-editor it would be neat to allow the user to add fields or configure individual fields.

As a workaround I now have a field and the user can add csvs to have a dropdown instead of an input. With Label:value syntax, but it feels a bit hacky.

@floelhoeffel
Copy link
Contributor

Hey Lukas,

Thanks for the input! Could you elaborate a bit more on the type of configuration you would like to see? When would that configuration be provided to the extension?

Thanks

@lukasoppermann
Copy link
Author

Hey Frederik,

sure I can try. So currently I can define have the user fill in a text field, set a boolean or select from an enum.

However, something like the tags input is not available. It is also not possible to build something where the user adds more fields. For e.g. you have an object with fields, you can not easily let the user define how the object looks.

A product might have a "product id", a "name" and a "price", while meta tags might only have "tag name" (maybe even as a dropdown) and "tag value". Allowing this in the configuration would be great.

@jelz
Copy link
Contributor

jelz commented Jan 17, 2019

This feature request was qualified for development and is now in our backlog, we cannot commit on any target date unfortunately.

@jelz jelz closed this as completed Jan 17, 2019
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

4 participants