Add unit tests for deep-link parameter validation

[Lakes41]

Difficulty: Intermediate
Type: test

Background
The README documents strict parameter validation for deep links: guild-detail links require a valid guildId, access-check links require both guildId and resourceId, walletAddress is optional, and invalid/malformed links should redirect to a user-friendly error screen.

Problem
There's no indication this deep-link parameter validation logic has dedicated unit tests, which is risky since Expo Router's file-based routing combined with custom-scheme and universal-link parsing has several edge cases (missing params, extra params, malformed URLs) that are easy to regress.

Expected outcome
The deep-link parsing/validation logic has unit tests for: valid guild-detail link, guild-detail link missing guildId, valid access-check link (with and without optional walletAddress), access-check link missing resourceId, and a fully malformed URL — each asserting the correct outcome (successful navigation params vs. redirect to the error screen).

Suggested implementation

• Locate the deep-link parsing logic (likely in app/ layout files or a dedicated src/ module) and add a test file under tests/ covering the matrix above.
• Use fixture URLs for both the custom scheme (guildpass://...) and universal link (https://guildpass.xyz/...) forms to ensure both are parsed identically.
• Assert that invalid cases route to the documented user-friendly error screen rather than crashing or silently no-op-ing.

Acceptance criteria

• Tests cover both link formats (custom scheme and universal link) for both link types
• Missing required params correctly trigger the error screen
• Optional walletAddress absence doesn't break access-check link handling
• pnpm test:run passes

Likely affected files/directories

• app/ (routing/layout deep-link handling)
• src/
• tests/

[jchinedu]

Hi! I'd like to work on this issue.

I have experience working with TypeScript and React applications, including writing unit tests for validation and routing logic. I understand how easy it is for deep-link handling to regress, especially when supporting multiple URL formats and required parameters.

For this issue, I'll identify the existing deep-link parsing logic and add a comprehensive test suite covering both custom scheme and universal links, valid and invalid parameter combinations, and malformed URLs. I'll ensure the tests verify the documented behavior, including redirecting users to the error screen for invalid links while allowing valid links to navigate correctly.

I'd be happy to contribute a clean, well-tested solution that follows the project's existing testing patterns.

[grantfox-oss]

🦊 GrantFox — @jchinedu has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #235)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.