-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iOS, macOS, and js support #23
Conversation
Use moko-resources to load common resources
use coroutines core in commonMain
For some reason composeable lambda functions on native macos throw an error and cause the application to crash. work around the issue by making result of composable lambdas non-null with the use of kotlin result
mapInput does not work on native. On native, you cannot catch the error when calling map with the wrong input type. Rework by passing the kclass to mapInput Store mappers in map of KClass to Mapper Also in the mapper interface add inputKClass and outputKClass. inputKClass is used to store a mapper in the new mappers (KClass to Mapper) map in KamelConfigBuilder
fix bitmap decoder import for android
just like in `Mapper`, in `Fetcher` store `inputDataKClass` for the input data class of each `Fetcher` and in `Decoder` store the class of the output of the decoder in `outputKClass` use these to pick a suitable fetcher in findFetcherFor and a suitable decoder in findDecoderFor
it hides the ExperimentalKamelApi opt in requirement
Load file resources with moko-resources
There was an import error on jvm Also add moko-resources test dependency and expose it as well
codestyles are set to kotlin official https://kotlinlang.org/docs/code-style-migration-guide.html
@alialbaali finished everything I wanted to do 🎉. I know you said you gave me permission to merge. But did you want to take a look first? |
kamel-core/src/commonMain/kotlin/io/kamel/core/utils/Platform.kt
Outdated
Show resolved
Hide resolved
Astonishing work you've done there! Thank you, really appreciated! 🎉🎉🎉 I don't have any issues at all, just a couple of things:
I personally don't mind, so please let me know your thoughts. 🙂 |
implementation("io.github.luca992.com.alialbaali.kamel:kamel-image:0.5-darwinandjs4")
|
|
fix moko-resources missed actual declaration
that works 👍 |
Alright then. Do you want to stick with the name Kamel? If so, what domain would you like us use? So far, I found these two:
|
I'd probably choose media if it were me. But your choice haha. And I think kamel is a solid name |
Alright. So, I got the domain, and the repository has been transferred to an organization. I'm guessing we're going to keep publishing on Maven Central, correct? If so, I think we might need a separate Sonatype Jira account where we can share the credentials? Or is it possible to invite someone to the project? |
Any thoughts @luca992? |
I don't think there's really any other viable option besides Maven Central anymore. And if you want to share credentials that's fine. You could make a bitwarden organization if you wanted to do that. But there's no way there's not a way to give multiple accounts permission to release to maven central for an organization.... however I have no idea how that works. Sonatype Jira is so confusing 🙃 maybe you can ask in the same ticket you use to create the new repository? |
I just need your Sonatype username, so I can let you publish artifacts. @luca992 |
Alright, I messaged you. |
Thank you guys for this great library! Curious if there is significant change in the usage/documentation? |
There shouldn't have been from this pr. The main README.md should be upto date |
This is a draft and not finished yet. But, I have begun adding support for iOS, macOS, and js targets!