I’ve noticed that Winden (or maybe it’s Plain Classes) won’t accept certain Tailwind conventions that are very helpful for use with page builders.
For example, if I attempt to create a custom utility class like this:
h-[calc(100%-3rem)]
I get an error message saying the utility class is malformed. But this is perfectly legitimate Tailwind syntax for custom styles via their utility class system.
I’ve also noticed that arbitrary variants and child selector syntax is also not accepted by either Winden or Plain Classes. Page builders often wrap modules in additional parent containers. It’s helpful to be able to write a utility class that targets the child of that parent wrapper so I can directly style the content contained within the module. But class nomenclature like this:
[&>*]:p-4
also causes an error. Again, this is perfectly legitimate utility class syntax for Tailwind, but I’m unable to use these sorts of classes with your plugin. As a more advanced Tailwind user, I find this to be a bothersome limitation.
Is there a way this sort of thing can be fixed?
purchase_id:
59499
Hi There, you need to update the Winden to latest version manually, as it is too much gap in version, from 2.0.2 to 2.7.3 latest,
And then you need to disable the Plain Classes Oxygen plugin, and then in the Winden settings, Enable the Oxygen Autocomplete and open any oxygen page and just click save and exit Oxygen, then it will do the compile fine,
If there is any other issue after that, reply here.
Regards,
Mohammad Arshad
DPlugins Support