-
Notifications
You must be signed in to change notification settings - Fork 109
Open
Description
The AmbientAware composable makes the ambient state available via two mechanisms:
- Via an AmbientState passed to AmbientAware's block argument. This is documented.
- Via the
LocalAmbientState.currentCompositionLocal (source). This mechanism does not appear to be documented.
Is there a reason for not calling this out? e.g. it's not recommended practice?
I'm not really sure what the convention is, although it does seem to satisfy the requirements/guidelines of the pattern. (It's cross-cutting, and intermediate layers should not be aware it exists. Also somewhat annoying to have to plumb through.)
Metadata
Metadata
Assignees
Labels
No labels