Process slots before processing subtree#200
Merged
Merged
Conversation
4f66498 to
476bad0
Compare
Contributor
Author
|
I also snuck in a change to fix the location of the |
Member
|
Oh boy I'm only now seeing this PR, just tested and you're right, we've had this bug all along! Thanks for adding the fix, will release a patch as soon as possible. |
Member
|
Published in v2.2.1, thanks again! https://github.com/posthtml/posthtml-components/releases/tag/v2.2.1 |
This file contains hidden or 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
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.
I attempted to use a component inside of another component like so:
When I did this, it didn't fill in any of the slots of the subcomponent.
This is the pipeline that the HTML goes through now:
Original:
expressions():processTree():You can see that by the time we reach the subcomponent, none of the slots are filled in, so they get removed entirely. My subcomponent has no
<yield>tags either, so that probably doesn't help.I reordered the pipeline to work like this
Original:
expressions():processSlotContent():processTree():Now, the component renders properly!