Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(trail): add number of campsites to trail #340

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

hamidhabib-buttons
Copy link
Contributor

Description

This feature adds number of campsites to a specific trail.

Screenshot 2025-02-10 at 9 19 38 AM

Fixes # (267)

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

  • Navigate to a specific resource page
  • Navigate to Camping section
  • Make sure the number of campsites are visible

Checklist

  • I have read the CONTRIBUTING doc
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have already been accepted and merged

@hamidhabib-buttons hamidhabib-buttons marked this pull request as ready for review February 10, 2025 14:52
@@ -8,7 +8,8 @@ create table if not exists rst.recreation_resource (
description varchar(5000),
closest_community varchar(200),
display_on_public_site boolean default false,
rec_resource_type varchar(50)
rec_resource_type varchar(50),
campsite_count integer default 0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we be storing a count of this as a column in the database or just query the count of defined campsites as we need them? This would work for MVP but we'd likely have to refactor it assuming there is a defined campsites section in the upcoming admin app.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason I put this alone as a single column is to avoid any unnecessary data storage in the recreation_resource table. For admin app, we can probably create another table and then just reference the table here in recreation_resource

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants