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

Support writing ticks and climbs to Aurora #20

Closed
lemeryfertitta opened this issue Feb 14, 2024 · 2 comments · Fixed by #26
Closed

Support writing ticks and climbs to Aurora #20

lemeryfertitta opened this issue Feb 14, 2024 · 2 comments · Fixed by #26
Assignees

Comments

@lemeryfertitta
Copy link
Owner

PUT /v1/ascents/

Data fields:

["uuid", "climb_uuid", "angle", "is_mirror", "user_id", "attempt_id", "bid_count", "quality", "difficulty", "is_benchmark", "comment", "climbed_at"]

PUT /v2/climbs/

"uuid", "layout_id", "setter_id", "name", "description", "is_draft", "frames_count", "frames_pace", "frames"

Need to determine how UUIDs for both ascents and climbs are generated.

@wetmore
Copy link

wetmore commented Mar 11, 2024

I believe the UUIDs are just UUID v4 without the hyphens. From looking at a few of them, they are 32 character hex digits and the 13th digit is 4.

@lemeryfertitta
Copy link
Owner Author

I believe the UUIDs are just UUID v4 without the hyphens. From looking at a few of them, they are 32 character hex digits and the 13th digit is 4.

Thanks! I came to the same conclusion. I have a work in progress PR for this, was able to get these working locally but went on a trip and haven't gone back to finish this up. I'll aim to release something soon.

@lemeryfertitta lemeryfertitta linked a pull request Mar 14, 2024 that will close this issue
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 a pull request may close this issue.

2 participants