o/hookstate: changes to enable running component hooks from the HookManager #13975
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
Needs Documentation -auto-
andrewphelpsj
force-pushed
the
component-hook-manager
branch
3 times, most recently
from
5497ac7
to
e2cc096
Compare
… interfaces can build a complete label expression, including component hooks
andrewphelpsj
force-pushed
the
component-hook-manager
branch
from
e2cc096
to
537a16f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change largely updates the hookstate package to enable running component hooks. At a high level, we add fields to the HookSetup struct to convey that a hook comes from a component, and we handle those properly.