-
Notifications
You must be signed in to change notification settings - Fork 11
SSR: Handle attribute directives separately from tag directives #140
SSR: Handle attribute directives separately from tag directives #140
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything OK codewise. Approved! ✅
By the way, I see that you started calling directives to both tags and attributes. The idea I had in that regard was that just the attributes were directives, while the tags were simply components (like in Web Components).
I mean, the names you used are OK. I guess we'll reach a consensus with the terminology anytime soon, haha. 😄
Thank you very much!
Yeah, this is something that I believe I've discussed with @luisherranz (I thought it was at #118 but I can't find it right now) -- it seemed to me like Luis preferred that nomenclature over directive/component. I'm fine with either -- maybe "component" is a bit more likely to be confusing, since it's used in so many different contexts 🤔
Indeed! 😄 |
It was actually @dmsnell the first one who started using it. I adopted it right away because I thought it makes much more sense. I think others (@SantosGuillamot? @michalczaplinski?) have also been using it lately.
You're totally right. We haven't discussed it anywhere. Sorry about that, David. I'll add it to the Tracking Issue: |
Follow-up to #133, addressing the following feedback:
(#133 (comment))
and
(#133 (comment))
attributes
andtags
inside bothsrc/directives/
andphpunit/directives/
.wp-directives.php
, use separate arrays for attribute and tag directives.process_wp_context_tag
andprocess_wp_context_attribute
.wp-context
attribute directive, as it's not implemented yet.