Added parking location on meetup detail page

[n-d-r-d-g]

Fixes #223.

@MrSunshyne I moved the meetup location info after Seats Limit to align the 2 locations on the same row. Feel free to suggest any changes.

Meetup with location:

Meetup without location:

Summary by CodeRabbit

Summary by CodeRabbit

• New Features

  • Enhanced event details with "Seats Limit" information based on attendee count and seat availability.
  • Added a "Parking Location" section with a link to view on a map if available, or a message indicating unavailability.
  • Updated label for the "Location" section to "Meetup Location" for clarity.

• Bug Fixes

  • Improved presentation of seating information by replacing commented-out implementation.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request enhance the Single.vue component by adding new conditional rendering logic for displaying seating limits and parking information based on the event's data. A new optional property, parking_location, has been introduced in the DirectusEvent interface to accommodate this feature. The layout adjustments ensure that the new sections integrate seamlessly with the existing structure while maintaining the functionality of the computed properties.

Changes

File Path	Change Summary
packages/frontendmu-nuxt/components/meetup/Single.vue	Modified template for conditional rendering of "Seats Limit" and added parking information section. Updated "Location" label to "Meetup Location."
packages/frontendmu-nuxt/utils/types.ts	Added optional property `parking_location: string

Assessment against linked issues

Objective	Addressed	Explanation
Add parking availability & location on meetup detail (#223)	✅

Possibly related PRs

• feat: add event location button to open map for events #234: Enhancements in the Single.vue component to improve the location section, directly related to the newly added parking information feature.

Poem

In the meadow where meetups thrive,
Parking spots now come alive! 🚗
With seats to fill and maps to view,
The event awaits, come join the crew!
A hop, a skip, let’s gather near,
For fun and laughter, bring good cheer! 🐇

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[cloudflare-workers-and-pages]

Deploying frontend-mu-nuxt with    Cloudflare Pages

Latest commit:	2e4b474
Status:	✅  Deploy successful!
Preview URL:	https://3e2e6ae1.frontend-mu-staging.pages.dev
Branch Preview URL:	https://feat-parking.frontend-mu-staging.pages.dev

View logs