* upgrade Reaktive to one that has better Apple Silicon support
* upgrade SQLDelight for Apple Silicon support
* Fix build to support Apple Silicon
Some of this code could be better centralized though I've been unable to
find a solution.
* simplify utils/build.gradle.kts
* workaround
* fix review comments
* sample todoapp: rename Todo.framework -> KotlinCommon.framework
Co-authored-by: dima.avdeev <dima.avdeev@jetbrains.com>
* Update examples to Gradle 7.3.3
Resolves#1654
* Update compose and agp in examples
Resolves#1117
* Fix gradle plugins classloading in examples and templates
* Make falling balls mpp compatible with examples checker
* move to kotlin 1.6.10-RC and corresponding compose commit
* Update path to the karma plugin we are patching
* Add ExperimentalComposeWebStyleApi
what worries me that this actually shows that there are some cases where without any changes apart version compiler people will have to worry about such annotations
* update kotlin version in templates to adopt 1.6.10-RC
* web: move ComposableWithNullableTypeParameter.kt to passing test cases
* update kotlin version in other places
* update imageviewer example: add OptIn for experimental API
* move compose
* move to kotlin 1.6.10 and corresponding compose
* move to kotlin 1.6.10 and corresponding compose
* move to 1.0.1-rc2
* move to 1.0.1-rc2 (todoapp)
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>
Co-authored-by: Shagen Ogandzhanian <shagen.ogandzhanian@jetbrains.com>
Remove:
```
__LATEST_COMPOSE_RELEASE_VERSION__
__KOTLIN_COMPOSE_VERSION__
System.getenv("COMPOSE_TEMPLATE_COMPOSE_VERSION")
```
They pollute templates/examples.
Now, all paths where we need to change the version are hardcoded in the script.
Usage:
```
./replace.sh 1.0.0-rc6
```
This script is planned to run on CI
In the future I will add support for changing Kotlin version
* Prepare the TodoApp example for adding the JavaScript app
* Add the JavaScript app for the TodoApp example
* TodoApp. Update Compose to 0.5.0-build225.
The verb `update` in `__UPDATE_COMPOSE_VERSION_MARKER__`
could be read as an instruction to update the plugin,
which might be confusing for users.
I suggest renaming the marker to more neutral
`__LATEST_COMPOSE_RELEASE_VERSION__`
Travis Reitter
Nikolay Igotti
Arkadii Ivanov
Alexey Tsvetkov
Igor Demin
Oleksandr Karpovich
Igor Demin
Nikolay Igotti
Oleksandr Karpovich
Javier Segovia Córdoba
Alexey Tsvetkov
Igor Demin