Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Fixes nested components and `<content>` tags. #619
As identified by #549, this fixes a bug with nested content tags by:
Making sure helpers are passed the same way as scope. Essentially parent helpers were not available. 586520c#diff-9ede961af024a842ba5e956318112b39R238 This was a bug waiting to be found.
Changing scanner to look all the way to content: 586520c#diff-08e58b9c9e7b5aea7a452a3e45ca998fR190. This would previously stop once it found a tags object, I needed it to keep going if it didn't find the actual matching tag.
Then I temporarily remove the tag.content callback while rendering the content. 586520c#diff-9ede961af024a842ba5e956318112b39R222 This is the core problem, that if you were rendering a