Do we have any methods that can extend custom element tags?

[cyz1901]

Hi @armanbilge. I really love Calico 😘. And after writing a demo, I think it's a good way to learn functional programming.
I am trying to combine Calico and the JavaScript ecosystem in the mobile product application to create more possibilities.

The type we use in DSL seems to be implemented based on the fs2.dom of the wrapper scala.js.dom

Usually, this is sufficient.
But when I combine some libraries, there are custom tags in the library.
For example, the nav in https://tw-elements.com/docs/standard/navigation/navbar/

  .evalTap(
      _.innerHtml.set(
        """
              <svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 24 24" class="inline-block w-5 h-5 stroke-current">
                <path id="heart-path" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M4 6h16M4 12h16M4 18h16">
                </path>
              </svg>
        """
      )
    )

But this not only looks ugly but also to some extent loses flexibility.

Do we provide other ways to extend new tags and write them in DSL?

like
lazy val nav: HtmlTag[F, HtmlElement[F]] = htmlTag("nav")

[armanbilge]

We have nav, it's actually called navTag.

https://www.javadoc.io/doc/com.armanbilge/calico-docs_sjs1_3/latest/calico/html/Html.html#navTag-0

We generate the elements using the scala-dom-types library. You can check there:
https://github.com/raquo/scala-dom-types/blob/04e66590f96216fe1e20036c4d9a32d59205526b/shared/src/main/scala/com/raquo/domtypes/defs/tags/MiscTagDefs.scala#L64-L78

[cyz1901]

Hey @armanbilge
What is our version distribution strategy？
I noticed that some commits have updated dependent versions, but it seems that these versions have not been released.

I added something for scala-dom-types

If merged, we will have a new version of scala-dom-types.

Should I create a new PR for Calico to upgrade the dependent version and release the new version for use in other projects?

[armanbilge]

Should I create a new PR for Calico to upgrade the dependent version

Has it been released yet? We get update PRs automatically as soon as new versions are released.

release the new version for use

I can cut a release after that update.

[armanbilge]

https://github.com/armanbilge/calico/releases/tag/v0.2.2

[cyz1901]

Should I create a new PR for Calico to upgrade the dependent version

Has it been released yet? We get update PRs automatically as soon as new versions are released.

release the new version for use

I can cut a release after that update.

I already megre pr in scala-dom-types. And scala-dom-types make a release later this week.
Is there any other way for us to add custom attributes directly in calico? This way I can skip the tedious publishing process.

[armanbilge]

In Calico you always have access to the underlying DOM element. So anything is possible, e.g.:

img().evalTap { i =>
  IO {
    i.asInstanceOf[js.Dynamic].crossOrigin = "use-credentials"
  }
}

With a little effort we can add some helpers to make it nicer. But your SDT changes will be released soon hopefully :)

[armanbilge]

But your SDT changes will be released soon hopefully :)

@cyz1901 https://github.com/armanbilge/calico/releases/tag/v0.2.2

[cyz1901]

The new version is amazing! lol