Aleksander Heintz
Aleksander Heintz
Also, if wanted, I can probably drum up a PR.
Or, better yet; `to_parts().map(PartTrait::to_string_lossy)`.
@oconnor663 would you want a PR for this? I could look into it if wanted - but I don't want to start working on this if you think it's not...
I'm not thinking of structure, just display tokens. But tokens, so they can be formatted as you please, with a built in simple default. So parts should probably be named...
None of those are problematic. If you read my transformation, it should be like this: ``` js React.createElement("tag-name", { "some": {a: 1}, "some.b": "2"}); React.createElement("tag-name", { "some.a": "1", "some": {b}});...
Let me clarify some more. This are not object expressions/merging. It's just treating the entire attribute (dots and all) as a string. So you can't do `attrs.some.a`, you'll have to...
@sebmck well, he said "conflicts and undefined behavior". Of which there are none.
@NekR it's not at all that it doesn't work. It's that I have a HTML element that expects an attribute with `.` in it's name.
@NekR No particular reason. It was made that reason a good while ago. It's a custom element, and I've been using it for a while. Now, I could obviously change...
@NekR I'd argue that those are fairly different though. One is an attribute, the other is an element name. Though, I've already stated my opinion. So I'll let the rest...