The definition of the leading property in the theme follows (Tailwind's responsive "leading" class definition](https://tailwindcss.com/docs/line-height#class-reference). However, as React Native doesn't know the rem unit or anything similar, Whirlwind simply multiplies the value defined in the theme by the font base size. That works for floating text and text using the base size but results in unexpected rendering issues when using a non-default font size.
To improve this, the following updates are proposed:
- Keep the responsive definitions for the time being, but document the shortcomings more clearly.
- Include new definitions
leading1, leading2, leading3, etc. that match the current padding and margin sizes. I.e. leading4 would match exactly the base font size, while leading8 would equal double the base font size, etc.
The definition of the
leadingproperty in the theme follows (Tailwind's responsive "leading" class definition](https://tailwindcss.com/docs/line-height#class-reference). However, as React Native doesn't know theremunit or anything similar, Whirlwind simply multiplies the value defined in the theme by the font base size. That works for floating text and text using the base size but results in unexpected rendering issues when using a non-default font size.To improve this, the following updates are proposed:
leading1,leading2,leading3, etc. that match the current padding and margin sizes. I.e.leading4would match exactly the base font size, whileleading8would equal double the base font size, etc.