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

• 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]

Walkthrough

The changes in this pull request enhance the event detail display in the Single.vue component by adding conditional rendering for seating information and a new section for parking location. The parking_location property is introduced in the DirectusEvent interface to support this feature. The label for the location section is updated to "Meetup Location," improving clarity. These modifications aim to provide more comprehensive event logistics without altering the existing logic significantly.

Changes

File Path	Change Summary
packages/frontendmu-nuxt/components/meetup/Single.vue	Added conditional rendering for "Seats Limit" and a new section for "Parking Location." Updated label to "Meetup Location."
packages/frontendmu-nuxt/utils/types.ts	Added new optional property parking_location of type `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: The changes in Single.vue regarding the addition of a link to view the parking location on a map are directly related to the feature introduced in this PR, which allows users to access a map for events.

Poem

In the meadow where meetups bloom,
Parking spots now dispel the gloom.
With seats and maps, we gather near,
Join us, friends, the fun is here!
🐇✨

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (4)

packages/frontendmu-nuxt/utils/types.ts (1)

64-64: LGTM! Consider adding a comment for clarity.

The addition of the parking_location property to the DirectusEvent interface is appropriate and aligns well with the PR objectives. The string | null type correctly allows for optional parking information.

Consider adding a brief comment to explain the purpose of this field:

+  // Optional field to store information about parking availability and location
  parking_location: string | null

This comment will help future developers understand the intent behind this property.

packages/frontendmu-nuxt/components/meetup/Single.vue (3)

110-119: LGTM! Consider standardizing the seats information.

The implementation of the seats limit information is well done and aligns with the PR objectives. The conditional rendering ensures that this section is only displayed when relevant data is available.

For consistency, consider standardizing the use of either Attendees or seats_available throughout the component. If they represent different concepts, it might be beneficial to clarify their distinctions in a comment.

---

137-151: LGTM! Excellent implementation of parking location information.

The addition of the parking location section perfectly addresses the main objective of the PR. The implementation is well-structured, consistent with other sections, and handles cases where parking information may not be available.

To enhance accessibility, consider adding an aria-label to the "View on map" link for the parking location, similar to the one used for the meetup location. For example:

- <a :href="getCurrentEvent.parking_location" target="_blank" class="uppercase text-xs text-verse-100 bg-verse-400 rounded-full p-2">
+ <a :href="getCurrentEvent.parking_location" target="_blank" class="uppercase text-xs text-verse-100 bg-verse-400 rounded-full p-2" aria-label="View parking location on map">

---

Line range hint 1-151: Great job implementing the parking location feature!

The changes in this file successfully address the PR objectives by adding parking location information and improving the display of meetup details. The new sections integrate seamlessly with the existing layout, and the use of conditional rendering ensures graceful handling of missing information.

As the component grows with more event details, consider breaking it down into smaller, reusable components for each section (e.g., MeetupLocation, ParkingLocation) to improve maintainability and reusability.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7056684 and f800b72.

📒 Files selected for processing (2)

• packages/frontendmu-nuxt/components/meetup/Single.vue (2 hunks)
• packages/frontendmu-nuxt/utils/types.ts (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

packages/frontendmu-nuxt/components/meetup/Single.vue (1)

124-124: LGTM! Improved clarity for location label.

The change from "Location" to "Meetup Location" enhances clarity and aligns well with the PR objectives. This specificity helps users distinguish between the meetup location and the newly added parking location.