andreyvolokitin

Will do a repo later if necessary, just checked — tag name indeed is not overwritten in the final output while other expressions are overwritten: https://i.imgur.com/bEVfwmq.png (final output shown in...

Yeah, expression like this: ```html {{text}} ``` with a ```posthtml.config.js``` like this: ```js module.exports = { plugins: [ require('posthtml-expressions')({ locals: { tag: 'a', text: 'Button', type: 'submit' } }), ],...

@jescalan could you explain this? I see this detail about tags was initially added in the readme by you (https://github.com/posthtml/posthtml-expressions/commit/3d04646f8d9574a76485c3fcea46af242be29e62#diff-04c6e90faac2675aa89e2176d2eec7d8R35). Is this because expressions themselves are made via custom tags?

I assume that is the case. The only question is — is it fundamentally impossible to overwrite ```node.tag```? I.e. [after all tag-logic is handled](https://github.com/posthtml/posthtml-expressions/blob/master/lib/index.js#L345), could it be possible to check...

I am trying to set up a frontend dev environment based on webpack which, amongst other things, would allow me to reuse HTML pieces. I am looking for something like...

Having some HTML-"components" library, there may be times when the root or some other tag within the component should be variable. I.e. with a button component — it can be...

> The way I see it, even if this were able to be implemented, this would be an extremely dangerous, and very infrequently used feature It can be hidden behind...

if/else means code duplication, which negates "components" approach, where there is a single source of "truth". Regarding ```href``` — I am really not sure, but it sounds like asking for...

Ah, and regarding always using `````` for buttons — I am afraid this would be impossible, because the most common thing is to use `````` for buttons, so that they...

> but if it is two lines that are duplicated in a single component, it can honestly end up being a non-issue, and not worth burning a large amount of...