update groups reg to be under event url

[diegoalzate]

overview

the reason behind this is to fix that when i click groups the navbar would have changed to the global links and not the event links.

Summary by CodeRabbit

• New Features
  • Enhanced routing structure to improve navigation by nesting group registration paths under specific events.
  • Updated routes for SecretGroupRegistration and PublicGroupRegistration to be accessed via :eventId/secret-groups and :eventId/public-groups.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
forum-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 2, 2024 10:40am

[coderabbitai]

Walkthrough

This update refines the routing structure in the application by nesting the /secret-groups and /public-groups routes under a dynamic :eventId parameter. This modification connects the group registration components more closely with specific events, improving the organization and clarity of the routing logic, which enhances the user experience when navigating between event-related pages.

Changes

Files	Change Summary
.../src/App.tsx	Removed standalone routes for /secret-groups and /public-groups; nested them under :eventId.

Poem

In a world of routes where I hop and play,
Secret groups now dance in the event's sway.
Public paths join in a joyful embrace,
Navigating events, a delightful chase!
So let’s celebrate, with a bounce and a cheer,
Routing’s more fun when friends gather near! 🐰✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4ba1d9c and 99fa00a.

Files selected for processing (1)

• packages/berlin/src/App.tsx (2 hunks)

Additional comments not posted (1)

packages/berlin/src/App.tsx (1)

250-257: Verify the correctness of the new routing structure.

The new routing structure nests the /secret-groups and /public-groups routes under a dynamic :eventId parameter. Ensure that the navigation remains consistent and relevant to the context of the event.