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

Reusable React Components timeline #3201

Closed
lunasabs opened this issue Jul 28, 2017 · 12 comments
Closed

Reusable React Components timeline #3201

lunasabs opened this issue Jul 28, 2017 · 12 comments

Comments

@lunasabs
Copy link

I'm not sure if this is the correct place to ask. If not, please lead me to the correct location.

In this article: https://medium.com/airbnb-engineering/caravel-airbnb-s-data-exploration-platform-15a72aa610e5
It is stated:

We’re planning on releasing the data visualizations and controls exposed in Superset as reusable React components. This modular approach will make these building blocks available to application developers. At Airbnb, we have many use cases for rich and interactive visualizations as part of of internal applications; for example, our A/B testing framework, anomaly detection framework and user session explorer. It would be great to share the same components across all of these applications.

When do you plan on releasing React reusable components? Or at least when is it planned to have the ability to embed without the use of iframes. This limitation is one of the only things stopping me from using this library right now.

@mistercrunch
Copy link
Member

We're hoping sometime in H2 this year. Keep in mind that the vision is to assume and leverage an existing Superset backend.

@robert-digit
Copy link
Contributor

So, just wondering here - how exactly will this happen when React is cat-x'ed by Apache foundation?

@xrmx
Copy link
Contributor

xrmx commented Aug 1, 2017

@robert-digit you have already opened an issue for that, no need to discuss it again here.

@mg1075
Copy link

mg1075 commented Dec 21, 2017

Wouldn't it be beneficial for more developers to make components with a framework agnostic approach, using a tool like Stencil?

... Stencil is also a solution to organizations and library authors struggling to build reusable components across a diverse spectrum of frontend frameworks, each with their own component system. Stencil components work in Angular, React, Ember, and Vue as well as they work with jQuery or with no framework at all, because they are just plain HTML elements.

@aaronhayes
Copy link

@mistercrunch any update on the time frame or progress?

@tkaklam
Copy link

tkaklam commented Jul 4, 2018

@mistercrunch also, if the feature is no longer prioritised, who could provide enough input to get others started on the topic? We're very interested!

@mistercrunch
Copy link
Member

I know I said the same thing a while ago, but I think this is coming some time over the next 6 months.

@aaronhayes
Copy link

@mistercrunch thanks for the update. Are you looking for outside contributions on this feature? Hopefully next quarter will be able to help out.

@mistercrunch
Copy link
Member

I think this runs pretty deep and would rather have seasoned committers to attack this. You can help by tackling simpler issues and features, and freeing core committers to work on more ambitious things.

We welcome all contributions of course but prefer new contributors to ramp up before taking on large efforts.

@TimHeckel
Copy link

@mistercrunch - hi! I'm simply wondering if there is an update on this functionality?

@mistercrunch
Copy link
Member

Check out the issues with the Superset Improvement Proposal label

@kristw
Copy link
Contributor

kristw commented Mar 28, 2019

Please checkout @superset-ui and @superset-ui/plugins-*

@kristw kristw closed this as completed Mar 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants