You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bruno-garcia do you think having two items is confusing, or is the main point that it takes too much space? FWIW, KMP has much more traffic (2x that of Kotlin on the landing page), so I kinda like having KMP called out explicitly. No strong opinions against merging, but I wouldn't want to use sub-platforms/guides as we do for Apple, it's a bit annoying to maintain and only really usable if most of the content is the same IMO.
SDK
Kotlin Multiplatform SDK
Description
We have two entries on the docs for Kotlin:
It takes space in the landing page as well as the drop down.
Kotlin docs is only a landing page to route the reader to either Android, Java or Kotlin Multi-platform: https://docs.sentry.io/platforms/kotlin/
It does that while showing
sentry-java
information the right side.Kotlin extensions, which lives under the Java docs, apply to Kotlin in general, including KMP.
https://docs.sentry.io/platforms/java/enriching-events/scopes/#kotlin-coroutines
Kotlin itself has one doc: https://kotlinlang.org/
It mentions its capabilities, including KMP.
Suggested Solution
I propose we merge both things into one area: Kotlin
Redirect all
kotlin-multiplatform
docs tokotlin
, and move all pages there.The landing page can have the same clarification that we have specific Android and Java (JVM) docs, including Spring Boot, elsewhere.
A smaller banner could live on top of all pages that are specific to KMP, with this clarification about Android and JVM docs.
An alternative solution is to include KMP as a sub-platform. Similar to how Apple/iOS is layed out:
We could then have:
Some other ideas I'm not very convinced about:
Perhaps the docs infra could make Kotlin point to Java, but just change the icon/URL otherwise to be Kotlin?
@kahest @HazAT @buenaflor wdyt?
The text was updated successfully, but these errors were encountered: