-
Notifications
You must be signed in to change notification settings - Fork 4
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
Late Provider: Handle unfulfilled Context Requests to handle Issues with Load Time & late Element definition #87
Labels
enhancement
New feature or request
Comments
quarkus
added a commit
that referenced
this issue
Mar 7, 2023
…s when a provider getx defined after a requesting child
quarkus
added a commit
that referenced
this issue
Mar 9, 2023
quarkus
added a commit
that referenced
this issue
Sep 19, 2023
…s when a provider getx defined after a requesting child
quarkus
added a commit
that referenced
this issue
Sep 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An idea wuld be to collect the requests on an global level and retrigger them at some time:
Lit does sth as well.
https://github.com/lit/lit/tree/main/packages/labs/context
There is an issue in the protocol as well:
webcomponents-cg/community-protocols#25
Where do we place / ship the global logic for the pooling !?
EDIT:
Easiest way is probably to retrigger the requests here:
element-js/src/BaseElement.js
Line 327 in 5ae7e17
The text was updated successfully, but these errors were encountered: