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

refactor dependencies in bundles and widgets #88

Open
erichanson opened this issue Nov 27, 2018 · 0 comments
Open

refactor dependencies in bundles and widgets #88

erichanson opened this issue Nov 27, 2018 · 0 comments
Labels
epic big meta-ticket that is more of an outcome than a specific task
Milestone

Comments

@erichanson
Copy link
Member

Right now, widgets have dependencies in the widget_dependency_js table, which fk's to widget and dependency_js. Then HTML resources often times import bundles which contain widgets and can then be called in. Also sometimes Javascript resources are stored not in the dependency table but rather as a static resource at /js/whatever.js. Bundles sometimes depend on other bundles' data, but there's no concept of dependencies between bundles. Refactor all of this.

Foremost, bundles need dependencies. Then, when a bundle depends on another bundle, they import it with a short-name alias, and can reference it throughout the bundle as such.

Then, maybe when we have server-side rendering of templates, we can just auto-generate the bundle import lines at the top of each HTML page? Regardless, that way dependencies are guaranteed to be met.

@erichanson erichanson added this to the 0.3 release milestone Nov 27, 2018
@erichanson erichanson added the epic big meta-ticket that is more of an outcome than a specific task label Apr 16, 2019
@erichanson erichanson removed this from the 0.3 release milestone Dec 27, 2020
@erichanson erichanson added this to the 0.3 release milestone Jan 15, 2021
@erichanson erichanson modified the milestones: 0.3 release, 0.4 release Jan 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic big meta-ticket that is more of an outcome than a specific task
Projects
None yet
Development

No branches or pull requests

1 participant