Repository navigation
Replies: 3 comments 5 replies
|
We have 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: |
|
Hey @armanbilge 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? |
Has it been released yet? We get update PRs automatically as soon as new versions are released.
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. |
|
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 :) |
@cyz1901 https://github.com/armanbilge/calico/releases/tag/v0.2.2 |
|
The new version is amazing! lol |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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.domof the wrapperscala.js.domUsually, this is sufficient.
But when I combine some libraries, there are custom tags in the library.
For example, the
navin https://tw-elements.com/docs/standard/navigation/navbar/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")All reactions