FlowContent and PhrasingContent separation is useless about kotlinx.html HOT 7 CLOSED

Very simple suggestion is to declare all tag-functions for the Tag class and discard *Content.
We'll have exactly one SPAN class and exactly one Tag.span function.

Pros:

• less code to generate
• simpler implementation, much easier to lean
• solves all the problems above
• minimal library, which does one thing (helps to write html from Kotlin)

Cons:

• hierarchy check still won't work

from kotlinx.html.

You can use FlowContent or HtmlBlockTag for that purpose. Just need to be documented

from kotlinx.html.

Just faced the same problem.
Wanted to create an universal helper that would be working both with divs and spans.

from kotlinx.html.

It is going to be fixed with upcoming release (will be aligned to kotlin 1.1 release)

from kotlinx.html.

@cy6erGn0m Just tested it. And yes, version 0.6+ works very well. Seems like you've completely refactored the inheritance architecture of the library. Thank you!

from kotlinx.html.

@kosiakk can we close it? Are your use-cases satisfied now?

from kotlinx.html.

Yes, FlowContent works for me now, thank you!

from kotlinx.html.