You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The packager currently can only handle modules with a default export.
Mid-term it should be possible to also handle modules that have multiple exports, or where the only component is nested in a normal export (which can be a valid coding style decision).
Braindump:
It should also be possible to handle mulitple exports, where some of the exports are not Landau components. Maybe it's possible to detect if a export subclasses Landau.Component?
Should the default rendering be to render all possible components, or that one specific component always has to be selected? "All by default" feels like the right approach, but might present problems on the performance side. It might also not be too pretty if all the components are centered on the origin, so that would either produce a big blob of components at the origin or we would have to take an opinionated stance on how to show them in an "exploded" way.
The text was updated successfully, but these errors were encountered:
The packager currently can only handle modules with a default export.
Mid-term it should be possible to also handle modules that have multiple exports, or where the only component is nested in a normal export (which can be a valid coding style decision).
Braindump:
Landau.Component
?The text was updated successfully, but these errors were encountered: