The Compose API guidelines outline the patterns, best practices and prescriptive style guidelines for writing idiomatic Jetpack Compose APIs. However, whilst this is available to still used via a modifier for other composables, readability is likely improved by the use of other padding modifiers that are available.API Guidelines for Jetpack Compose Last updated: MaWho this document is for The PaddingValues class itself is an argument that can be passed to certain composables (Scaffold and Button are to name a few) – this allows you to add padding directly to the content area of the composable without needed to directly apply modifiers. Under the hood, this modifier utilises the exact same PaddingModifier class as the other padding modifier functions – meaning that setting an PaddingValues in this way is the same as using the Modifier.padding(all: Dp) function. The main difference being the value that is provided for the rtlAware argument – for absolutePadding this value is provided as false, whereas the default padding modifier provides this as true.Īlongside the above approaches for applying padding, there is a padding modifier which takes a reference to the PaddingValues class:įun Modifier.padding(padding: class PaddingValues(

Under the hood, the absolutePadding and padding modifiers user the same Modifier class to construct the composable padding. For this we can utilise the absolutePadding modifier – this allows us to define padding values for all edges of a composable, specifically the left and right edges instead of the start and end: However, in some cases we may wish to apply padding without this awareness of righ-to-left layouts. With the above padding approaches, right-to-left layouts are accounted for – we can see this via the use of the start and end arguments.

Internal kotlin modifier