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

Additional Render Strategies #105

Closed
elbakerino opened this issue Mar 27, 2021 · 1 comment
Closed

Additional Render Strategies #105

elbakerino opened this issue Mar 27, 2021 · 1 comment
Labels
enhancement New feature or request plugin
Projects
Milestone

Comments

@elbakerino
Copy link
Member

The core should already support multiple render strategies, it's just a matter of reusing base components.

For an example and as it provides some special flexibility for some use cases, currently thinking about survey schemas, an additional strategy renderer similiar to jsonforms.io would be great, example of category schemas.

Should reuse #104 for view into data schema merging.

@elbakerino elbakerino added enhancement New feature or request plugin labels Mar 27, 2021
@elbakerino elbakerino added this to To do in ui-schema via automation Mar 27, 2021
@elbakerino elbakerino added this to the v0.3.0 milestone Jul 4, 2021
@elbakerino
Copy link
Member Author

With 0.3.0-alpha it is now possible to implement any render strategy, bind a custom WidgetRenderer to widgets.WidgetRenderer, maybe reuse the matcher function: widgetMatcher. Then with the own WidgetRenderer, someone can replace ObjectRenderer/VirtualWidgetRenderer with own implementations.

Reusing the core functions will be further optimized in 0.4.0 with #100.

ui-schema automation moved this from To do to Done Jul 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request plugin
Projects
ui-schema
  
Done
Development

No branches or pull requests

1 participant