Remove empty object from configuration to work with tailwind default …

[lusimeon]

…values

Remove empty object from configuration because it removes default values from tailwind to be generated in compiled file.
Actually, all CSS rules overwritten with empty object are not availables.

[titouanmathis]

@lusimeon it was actually a deliberate choice to remove them in order to generate smaller files for projects not using Purge CSS.

But your PR makes me wonder if it was a good choice. Purge CSS can be added quite easily to any project, and it might be usefule to have all Tailwind CSS classes available to avoid jumping between their doc and our configuration.

I personnaly would approve this PR, but I would like to have some feedback from the whole @studiometa/css team :)

[perruche]

yeah that's probably a good idea to avoid confusions.
Should we keep all the object keys in the file ?

[lusimeon]

@titouanmathis I understand, maybe we can remove only one of thoses rules (like grid-layout related), however fontWeight or lineheight and some others seems necessary on every project.

Anyways, the correct way to disable a rule is to set it to false on corePlugins property.

[titouanmathis]

Let try a minimal configuration and keep the management of things to disable in each project.

These modifications will be published in the v1.0.0-alpha.3 version.