-
-
Notifications
You must be signed in to change notification settings - Fork 384
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
Prepare all the things #3319
base: main
Are you sure you want to change the base?
Prepare all the things #3319
Conversation
430cdce
to
a0a4f95
Compare
Can you help me understand a bit more of what we want to achieve here? The original plugin design was to allow anything synchronous (e.g., preloading, loading styles, etc) in the module to happen independently, in parallel, and in a mostly indeterministic manner to every other module.... maybe that was a bad thing? I'm worried that |
All As we've access to It'll also add consistency in how plugins and their state are managed. For example with core/biblio: earlier even if we called It terms of clarity, also see how we removed an unnecessary async-await with |
I'm not really liking the |
I like this idea in principle. |
No description provided.