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

Recently added area displays incorrect number of subareas and climbs #877

Open
josh610 opened this issue Jun 16, 2023 · 2 comments
Open
Labels
bug Something isn't working

Comments

@josh610
Copy link
Contributor

josh610 commented Jun 16, 2023

Steps to Reproduce

  1. Create a new area and new crags within it, and populate them with climbs.
  2. On the parent page of the new area, listed areas are shown as having 0 sub-areas.
Screen Shot 2023-06-16 at 1 35 49 PM
  1. On the parent page of the new crags, crags are shown as having 0 climbs.
Screen Shot 2023-06-16 at 1 46 30 PM Screen Shot 2023-06-16 at 1 58 19 PM

Screenshots are from this area.

Expected Behavior

Listed areas/crags should display correct number of sub-areas or climbs

Current Behavior

Listed areas/crags display 0 sub-areas or climbs, despite having >0

Browser & version

Chrome 114.0.5735.133 (Official Build) (arm64)

Operating system

MacOS 12.5

@musoke
Copy link
Contributor

musoke commented Jun 16, 2023

This is similar to OpenBeta/openbeta-graphql#213. I suspect that something similar to the in progress OpenBeta/openbeta-graphql#314 will work for this too.

@vnugent
Copy link
Contributor

vnugent commented Jun 17, 2023

I created a backend issue: OpenBeta/openbeta-graphql#319

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants