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

Gyms are not treated as TLC #2242

Closed
nicHoch opened this issue Jun 27, 2016 · 3 comments
Closed

Gyms are not treated as TLC #2242

nicHoch opened this issue Jun 27, 2016 · 3 comments
Assignees

Comments

@nicHoch
Copy link
Contributor

nicHoch commented Jun 27, 2016

Index top down first Gym (no other crags above) are not marked as TLC.
The API index detail endpoint does not provide a TLC ID for that gyms.
Also in the App some functions are triggered by that TLC information. I could implement an exception for gyms but would be happy for a more general solution.

@scd
Copy link
Member

scd commented Jun 30, 2016

We need to nut out gyms.

  • Yes they should be the TLC if there is not already an ancestor TLC.
  • We should be able manage and download gyms as their own package even if there is a TLC ancestor.
  • If a gym is paying they need special status in the app.

@birgander2
Copy link

Is there a reason why normal crags are not downloadable as their own package even if there is a TLC ancestor? I mean, some of the TLC are really huge and one might prefer to download only a subpackage of it.

@brendanheywood
Copy link
Member

The TLC and the download issue should both be solved already

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

No branches or pull requests

4 participants