Open LaatonWalaBhoot opened 10 months ago
Sounds like a good idea! The way I would like to think about this is,
Would it not make it difficult to maintain? Having to provide feature updates to both libraries? As far as I understand if we can achieve consistent behavior then dependents won't have any issues no? Agree on the tests part.
Crux exports both Jsoup and OkHttp as API dependencies, and also returns native JSoup objects. So moving to KSoup will be a breaking change for all clients.
Since many clients already use JSoup, we cannot reasonably expect everyone to fully move over to KSoup, even after it reaches full maturity.
Do I publish the KMP library separately from this? I will link it to Crux and give credits. Or is there an alternative that you can propose since functionality will be almost similar?
It’s possible to have two or more separate libraries published from the same repo; that seems like a preferable approach so that everything stays in one place, and still can be optionally imported by clients.
@chimbori Have raised PR #30. Please take a look
As the title says. Provisions for KMP support by moving from OkHttp to Ktor And Jsoup to https://github.com/fleeksoft/ksoup I would be happy to provide a PR and contribute to this. Would anyone be interested in helping out?