[Fix] inputClassName, containerClassName, and toggleClassName accept functions...

[giero]

… to override component className (#64)

This is another (i think better) approach after #68.

Now we will be able to do sth like this:

inputClassName={(className) => twMerge(className, "dark:bg-blue-100")}

and twMerge is no longer needed inside react-tailwindcss-datepicker :)

Also fixed some minor bugs and removed unnecessary code.

[onesine]

@giero, I think we are starting to have too many props for classes. We can group them all in the classNames props. But we'll have to leave the ones that are there so that those who already use the library with these props won't have problems with updates.

Thank you for this PR

[giero]

If you want I could adapt classNames for the same purpose as my changes for individual fields and restore them to strings only (to avoid problems with updates)?

[onesine]

OK, that would be great.

[onesine]

The same problem can occur if the user uses strings on the inputClassName, containerClassName and toggleClassName props.

[onesine]

Same thing for this line

[onesine]

I think there will always be problems with this line.

If in containerClassName we have text-red-400 then it will conflict with text-gray-700 of defaultContainerClassname.

[giero]

Yes, and that's why I offered to use tailwind-merge to solve this issue in #68. To avoid adding it to the library, containerClassName (and other "class names") became functions to allow users to use twMerge (or other library) outside the datepicker.

But yes - if containerClassName is a string there still will be issue with this ... I left this to avoid BC break.

[onesine]

In case containerClassName is a

• string we want to style the container with only its own utility classes then we don't need twMerge
• function we want to add utility classes to the existing ones, then we may need twMerge to avoid conflicts.

When containerClassName is not defined, we use the default style.

[onesine]

Same thing for this line

[JshGrn]

Whats the latest with this because I do not want to use your theming classes...

[onesine]

In case containerClassName is a

• string we want to style the container with only its own utility classes then we don't need twMerge
• function we want to add utility classes to the existing ones, then we may need twMerge to avoid conflicts.

When containerClassName is not defined, we use the default style.

@giero

[giero]

@onesine I updated this PR to apply your suggested changes. So providing inputClassName/containerClassName/toggleClassName as strings will override existing default styles. Using them as functions will allow to use default styles with some external class-merge-tool (like twMerge) by user.

[onesine]

I should see this but I couldn't. So sorry @giero . You can resolve the conflicts and republish.