Hey @rjvim! 👋

You're right, tailwind-merge should ideally remove the p-3 class here. The reason why it is not removed is following:

1. tailwind-merge allows refinements. That means if you do twMerge('p-3 py-2') or twMerge('p-3 px-4'), both classes are preserved. I'm doing this because if you add py-2, you probably still want to keep the vertical padding p-3 provides.
2. Adding a check for when all refinements of a class are present to remove the base class would slow down tailwind-merge at runtime and add to its bundle size. So I'd only add this check if it is really necessary.
3. Tailwind CSS specifies its classes so that these refinements like py-2 and px-4 always override classes like p-3. That means if we leave the p-3 class in there together with py-2 px-4, it will have no effect as vertical and horizontal padding will be overridden. That in turn means that we don't need to remove that class with tailwind-merge.

Hope that explanation helps. But I have to admit that it looks weird to leave the p-3 class in there. If I find an easy way to remove it within tailwind-merge, I'll probably do it. 😊