How are we supposed to determine the name of a dep...
# react
m
How are we supposed to determine the name of a dependency provided by the kotlin-wrappers version catalogue? It doesn't seem obvious from the kotlin-wrappers docs. And they don't all follow the same pattern. We mostly relied on intellij auto-complete.
t
And they don't all follow the same pattern
Do you have example?
We mostly relied on intellij auto-complete.
From
kotlinWrappers.
?
Mike, to avoid long reviews it will be cool to split PR
1. Subproject (empty) 2. Small app 3. Tests (run in browser) 4. Node.js tests configuration
m
That's kind of how I was doing with my own commits 🙂 1. Copy tanstack-react-router example 2. add trivial test 3. add node test config (ran out of time) If you would prefer I do each commit as a separate PR, I can do that.
It'll just look weird to have an example that doesn't do what it claims in the intermediate steps
Yes, we used itelllij auto-complete from From
kotlinWrappers.
in build.gradle.kts
t
If you would prefer I do each commit as a separate PR, I can do that.
Yes, please
Yes, we used itelllij auto-complete from From
kotlinWrappers.
in
build.gradle.kts
That is why we created version catalog 😉
It works without docs 😉
> And they don't all follow the same pattern What do you mean?
m
kotlin-react-dom -> kotlinWrappers.reactDom kotlin-emotion-styled -> kotlinWrappers.emotion.styled kotlin-mui-icons-material -> kotlinWrappers.mui.iconsMaterial kotlin-tanstack-react-router -> kotlinWrappers.tanstack.reactRouter kotlin-testing-library-react -> kotlinWrappers.testingLibraryReact Sometimes it's (camel-case main lib name).(camel-case subproject) Sometimes it's (camel-case main lib name and subproject)
t
It depends on NPM coordinates. We should respect NPM organizations to avoid clashes.
@emotion/styled
->
kotlinWrappers.emotion.styled
emotion-styled
->
kotlinWrappers.emotionStyled
@tanstack
,
@mui
,
@emotion
- NPM organizations
m
Ah, That makes more sense. Thanks for explaining it.