feat: add html attributes to cards

[iNeoO]

#434

I believe all valid HTML attributes for a

should be allowed on the Card component.
I removed the type assertion. I'm not sure why it was there in the first place.

[ddecrulle]

Hello,

Thanks for the proposal.

The type assertion is intentional. It ensures we destructure all props explicitly, so nothing is unintentionally passed via rest. Without this, rest wouldn’t be inferred as never, and we could accidentally miss props without noticing.

We do spread rest onto the <div> to allow custom or non-standard HTML attributes, but that naturally leads to type issues that user needs to explicitly ignore.

To resolve this without compromising type safety, I’d suggest introducing a dedicated prop nativeDivElement. That’s consistent with the pattern we’ve followed elsewhere in the codebase, and it allows us to keep the Equals<keyof rest, never> check valid and meaningful.

[iNeoO]

Hmm, I'm not really convinced it's worth doing the assertion, but I made the change you asked for.