I’m seeing some behavior that I think might be a bug. It seems like `LayoutModifier`s are only being...

# compose

[Zach Klippenstein (he/him) [MOD]]

I’m seeing some behavior that I think might be a bug. It seems like `LayoutModifier`s are only being calculated when they’re first applied to a node, and any changes in subsequent compositions don’t actually update the layout.

E.g. I’m trying to move a composable around by passing a custom Alignment implementation that just takes a fraction and aligns to that fraction of the parent. The initial alignment is calculated correctly, but when the fraction changes in subsequent compositions, the composable’s position doesn’t change.

Will file soon.

[Zach Klippenstein (he/him) [MOD]]

So it’s not layout modifiers, it’s just alignments. Here’s the bug and repro code: https://issuetracker.google.com/issues/169982630

repro.mp4

[Zach Klippenstein (he/him) [MOD]]

I know custom `Arrangement`s are no longer supported, are custom `Alignment`s destined for the same fate? I don’t care too much either way, but I’ve written this FractionalAlignment a few times now, could be useful to have in the library.

[Mihai Popa]

are custom `Alignment`s destined for the same fate?

Nope.

could be useful to have in the library.

Yes, adding it to the library is planned.

[Mihai Popa]

Also thanks for the bug, looking into it 🙂