bug: deleting the default card leaves user with no default card — next card should be auto-promoted

[anusuyasri]

Hi, I'd like to work on this under GSSoC '26! I've reviewed the cards.ts source and confirmed that the DELETE /:id handler has no logic to promote another card as default after the default card is deleted. I'll add the auto-promotion logic, handle the edge case where the deleted card is the last one, and add a test covering this scenario. Please assign this issue to me.

[aksharaa1912]

Hi

I would like to work on this bug. Fixing the incorrect 409 conflict error on the cards endpoints is important because it prevents users from saving or updating their cards due to a false "Username already taken" validation block, directly breaking core application functionality.

My approach to resolve this:

1. Locate the POST and PUT controller logic for the cards route.
2. Investigate the validation middleware or database query that handles the unique constraint checks.
3. Isolate why the user schema validation (username check) is triggering during card creation/modification.
4. Correct the logic so it validates card constraints instead of user credentials, and verify the correct HTTP status codes are returned.

Could you please assign this issue to me? Thanks!

[Midoriya-w]

Hey @Harxhit! I'd love to work on this under GSSoC 2026. I'll fix the P2002 catch block in cards.ts to return a card-appropriate message, verify users.ts still handles its own 409 correctly, update the README Error Cases table, and add a test. Can I get assigned?

[Harxhit]

@anusuyasri I have assigned this issue to you.