compose-jb

1255 Commits

247 Branches

378 Tags

412 MiB

Tree: 58be35e880

Commit Graph

Author	SHA1	Message	Date
Oleksandr Karpovich	e902beeece	release 1.0.1-rc2 with 1.6.10 (#1590 ) * 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>	3 years ago
Igor Demin	dbd0a21949	Modify replace.sh for replacing Compose version (#1511 ) 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	3 years ago
Oleksandr Karpovich	8c01295e8a	Web/add compose plugin integration cases for kotlinjs (#870 ) * web: Add integration cases for compose plugin targeting kotlin/js * web: Add integration cases for compose plugin targeting kotlin/js * Report cases to TeamCity * Update README.md Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>	3 years ago

Author

SHA1

Message

Date

Oleksandr Karpovich

e902beeece

release 1.0.1-rc2 with 1.6.10 (#1590 )

* 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>

3 years ago

Igor Demin

dbd0a21949

Modify replace.sh for replacing Compose version (#1511 )

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

3 years ago

Oleksandr Karpovich

8c01295e8a

Web/add compose plugin integration cases for kotlinjs (#870 )

* web: Add integration cases for compose plugin targeting kotlin/js

* web: Add integration cases for compose plugin targeting kotlin/js

* Report cases to TeamCity

* Update README.md

Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>

3 years ago

3 Commits (58be35e8807eca00ff53165ec9d54dce2918793b)