Conception of API with more modifiers and environments variables

[pylapp]

Context

Today, we define our components following the Figma specifications and do our best to be aligned with the notions of design assets.

For example, for a checkbox component (v0.21.0 of the lib), its init is a bit verbose:

    public init(isOn: Binding<Bool>,
                accessibilityLabel: String,
                isError: Bool = false,
                isReadOnly: Bool = false) {}

Using the init is interesting here for several uses:

• force user to add a value when he/she integrates the component (e.g. here accessibilityLabel)
• let user get the state of the component (e.g. here isOn)
• it eases also the documentation of the component and the tests

However this way to do, even efficient, is a bit verbose, not enough reactive / swifty.
We can imagine to use specific view modifiers for the component which will, for example ad a specific value as environment variable. View modifiers, styles or environment methods can be used.

For example:

OUDSCheckbox(isOn: $isOn, accessibiltyLabel: "Some label")
.modifier(OnError())

Solution

Check if the two approaches can be used in the same time.
Otherwise see which one is the best for the users and keep in mind the tests and the documentation.