Open lord007tn opened 4 months ago
@lord007tn Thanks for bringing it up
Are you gonna add a CLI feature
Or gonna change the source code classes from directional properties to logical properties?
The CSS Logical Properties support table seems fine
https://caniuse.com/css-logical-props
Vite browserlist config https://github.com/vitejs/vite/blob/37af8a7be417f1fb2cf9a0d5e9ad90b76ff211b4/packages/vite/src/node/constants.ts#L19
Think that logical properties is better, thanks for the PR)
@sadeghbarati i will make a pr soon to change direction properties to logical properties as it seems to support i18n with multi direction website
Another note, that space-x-*
won't work on RTL direction. a good replacement is gap-x-*
if the container already is flex/grid.
any updates on this?
Created a poll here please share it for others
Coming back to this issue after a few months, could we extend the tailwind prefix
functionality, to transform the component on the fly, based on user preference, before deploying them to the user machine?
Describe the feature
It seems that components use left and right values from tailwindcss i would recommend using start and end so it supports RTL and LTR directions in projects
so instead of
pr-1
,ml-2
... we usepe-1
,ms-2
And so onalso in components that have Chevron icons we should add
rtl:rotate-180
class so we make sure when we change direction arrow rotateTasks:
start-, end-
/ps-, pe-
/ms-, me-
/ ... ) instead of (left-, right-
/pl-, pr-
/ml-, mr-
/ ... )Additional information