Also; given that shared sourceSet seems to be the ...
# multiplatform
d
Also; given that shared sourceSet seems to be the new-world approach to multi-platform, isn't the tutorial here: https://kotlinlang.org/docs/tutorials/native/mpp-ios-android.html#creating-the-shared-module ...just plain out-of-date, or a lesser advised alternative, and therefore harmful to adoption? Confusing newcomers (me) is never a good look. I feel like given the change that occurred, they should at least be explicit about it, in a foot-note.
💯 1
j
I was trying to figure out how to create a multiplatform module using kotlin-dsl with Gradle and didn't figure it out either
And I also was trying to follow that page which is outdated
1
d
I'm getting there but it looks like the documentation is really lagging behind the fast pace of development at the moment. Few examples are showing the latest way of doing things (e.g.
val iosMain by getting {...}
pattern)
A little surprised at JetBrains on this one; outdated tutorials are only going to undermine all the good effort they're putting into developing cross-mobile dev tools.
It doesn't cost much to pull them, or mark them out of date.
r
It evolves very fast. A new documentation for the current state would be outdated in 2 weeks. Outdated documentation is acceptable for me at this point.
Hmmm I should update it.
j
That's pretty helpful thanks, I'm gonna try again referring to yours
r
I edited my gists. They’re now very close to what we have in production.
👏 1
In the iOS app MPP project, I state that there is no source in the project but we still need at least one file so that it compiles. It’s no longer the case for us, as we’re now writing the majority of the app in Kotlin. It’s kinda mandatory. If you use Swift, then you can’t use generics nor coroutines.
d
Nice, thanks for the info & example updated, @ribesg