Pavel Holec

Some illustrations got obsolete and should be removed: - TimelineBoarding - TransportTaxi

Concatenating 2 headings does not respect the biggest out of concatenated heading vertical paddings and causes resizing glitches in snapshots.

Updating Storybook previews is time-consuming, mostly duplicate effort. There might be a way to be able to reuse previews in storybook target without having to exposed those previews in non-preview...

Use native SwiftUI environment keys

1

Some components might use existing environment keys or modifiers in favour of parameters. #### Available related environment keys - #401 - #404 - `lineLimit`, `lineSpacing`, `multilineTextAlignment `, `textCase`, `truncationMode `:...

Components could be decomposed to separate public parts for better reusability and flexibility. We would still keep the convenience standalone component, but it would be a thin wrapper over its...

Decide on which parts of components should accept styling such as `textColor` or `fontWeight` provided by call site. For some components, only some styling is meaningful, while the rest should...

Animation of selectable components should be slow in, fast out (so that when switching between selections, there is no 2 selected options at the same time visible)

This would enable the support for concatenation of a text that has a specific background. The native support in AttributedString is not enough (it uses the background for the newline...

`isSelected` trait seems to be missing. Other accessibility properties should be rechecked as well.

Actions that do not return value (such as shouldReturnKey) should be all able to be run in sequence to avoid passing the handler. The technique works by reassigning the closure...