Workaround Scalatags' problems about scalajs-react HOT 4 CLOSED

I typically want one of 3 things:

1. No dom building stuff.
2. All html tags and attrs with no prefix.
3. All html tags and attrs with prefix.

Separately, I sometimes need access to Tag and Modifier for fn args.

I Imagine something like this:

• I only want tag and modifer. - import x.{Tag, Modifier}
• All, no prefix. - import x._ - Scope: implicits._, tags, attrs, no tag/modifier.
• All, on prefix. - import x._ - Scope: implicits._, *, no tag/modifier.

That would change

import japgolly.scalajs.react._, vdom.ReactVDom.{Tag => _, _}, all._

into something like

import japgolly.scalajs.react._, blah._

It may be a good idea to rename Tag and Modifier and bring them in via react._.

from scalajs-react.

Speaking of prefixes, < for tags and * for attrs looks awesome. It really makes the tags jump of the page in a sea of Scala. Make that possible for people like me.

from scalajs-react.

Changed * to ^ because of utest.*, plus ^ implies meaning when each attr on new and indented.

Next:

• Moved into main import? (ie. import japgolly.scalajs.react._ instead of import japgolly.scalajs.react._, vdom.prefix_<^._)
• Deprecate and advise against vdom.all._?
• Update doco.

from scalajs-react.

Fixed in 87793b1. Yes!!!!!

from scalajs-react.