FYI if upgrading to newest Canary 13 while using D...
# mvikotlin
j
FYI if upgrading to newest Canary 13 while using Decompose the mpp/compose workaround needs to be updated to reflect the new compose compiler location refactor:
Copy code
project.dependencies {
        composeCompiler "androidx.compose.compiler:compiler:$compose_version"
    }
there are "phi errors" in the build for material packages that I can't make heads or tails of though
a
So does it work?
j
I haven't noticed any issues just yet
it's specifically referencing viewPager jar that I'm not using in the app
a
You mentioned "phi errors", looks like not so important?
j
they presented as warnings in the build but the text said "Phi error with register 6" or "register 37". The warnings have not shown up after the first build. All tests have passed and the app is working as expected
I have decompose pulled, let me see if I can get the errors on the todo sample
this is the warning
a
Ok, looks like just warnings
Thanks! Would you mind submitting a PR with the update?
j
Absolutely, will do
a
Thanks!
j
Those warnings must mean something, the Modifier.weight function isn't recognized
I don't see anything in release notes and it's marked as @Stable
a
Worth to ask in their channel. Heard that the new alpha is buggy.
j
It was new implementation detail for ColumnScope / RowScope modifiers to avoid them being used where they'll be ignored
those modifiers need to be used within
with(ColumnScope){ Modifier.weight() }
a
Nice catch!
j
How can I open a PR on the project, I'm used to enterprise where I can push up a branch
a
Basically you need to fork the repo, clone it to your local machine and add upstream remote. Then create a branch, commit and push to your repo. Then you will see a button if you open the original repo.
j
Thank you