Hey all, why is this coming up as a val?

# compose

[Brian Donovan]

Hey all, why is this coming up as a val?

[jim]

IIRC in Kotlin, function parameters are always immutable references

[Brian Donovan]

ty

[Brian Donovan]

I am trying to show a circular spinner once I click on the Log In button but nothing is happening

[Brian Donovan]

[Brian Donovan]

[Brian Donovan]

it’s always in the if block no matter how many times I click the Log in button

[jim]

What happens if the login fails due to a connection issue?

[jim]

Without looking closely at your code, I get the sense you are creating some source of truth issues.

[jim]

I'd suggest you consider re-reading the sections on "unidirectional data flow" and "state hoisting" and ensure you are following those principles

[Brian Donovan]

Right now there is no connection, I am just trying to make the UI work. Switching the button to a spinner onClick

[Brian Donovan]

I was going to worry about that later

[Brian Donovan]

I just don’t know why this condition isn’t working

[Kirill Grouchnikov]

The Compose way is for the "caller" of LoginButton to provide a lambda that is called in your onClick . It is the caller's responsibility to update the source of truth for the state, not this composable.

[Kirill Grouchnikov]

This is a "flattened" example of this - but in the real app the state would be managed outside of this composable function, and this function would get the current state and a lambda to call in onCheckedChange (where the lambda updates the state and that causes recomposition of your composable)

[Brian Donovan]

ty, I will look this up

[Abhinav Suthar]

Please confirm if isDisplayed is a state variable