-
-
Notifications
You must be signed in to change notification settings - Fork 113
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
Importing Ticks/Ticks Testing #525
Comments
|
I did not add a button to the profile pages, and yes the ticks will be viewable once I finish the standalone ticks page. I will add a button to the profile page so we can get the modal back. I spaced on that. Adding the button to get the notification back, and a way to view individual ticks right now. |
Multiple ticks are going to be supported. I will be adding a modal that shows the current ticks of a route and within this modal you will be able to tick it again. |
This feature has been pushed to our "canary branch" you can access it by putting http://stg.openbeta.io/?next=true in the URL Please mess around with this and let me know of anything you think would be ideal to add or any bugs/improvements you find. |
I was able to import without any problem. It'd be nice to have a crude "view my ticks" page to review my ticks. Filed #576 |
I will hop on a view my ticks page in the coming weeks! |
Not sure if this is the right place to log this, but I'm consistently getting an error when attempting to use the tick import feature for duplicate ticks, something like this:
Maybe I am just misusing the tick feature on Mountain Project, but apparently I've added a tick for each attempt/lap on routes on the same day, so I have multiple instances of ticks from the same route and same date. |
Thank you for the report @itsmattsoria ! It looks like this is the same issue as #631? Good to see another data point confirming my hypothesis. |
I think this is the root cause: OpenBeta/openbeta-graphql#175 |
Not a problem @itsmattsoria, I'm just happy to see progress |
@itsmattsoria we recent made a fix to allow multiple ticks of the same climb on the same day (OpenBeta/openbeta-graphql#340). Can you please try again? |
@vnugent works like a charm! |
I'm closing this. FYI we're now tracking our work on a unified project board: https://github.com/orgs/OpenBeta/projects/8/views/2 If you have ideas or feature requests, please do share by filing a new issue. |
Hey there guys. I have recently added a feature that allows you to import ticks from mountain project, and tick your own climbs. All of this information should persist in our staging GraphQL database, so if you are interested in testing it out slide on over to https://graphiql-online.com/ and put in the staging endpoint https://stg-api.openbeta.io. Below I am going to list what I think should happen when using this feature, and what is to be expected from it in the future.
If you have not imported your ticks from Mtn Project, and have not clicked the 'Don't show again' button, you should be met with this notification when visiting a climb.
![Screen Shot 2022-09-06 at 9 08 47 AM](https://user-images.githubusercontent.com/24400646/188686016-2518a0f4-00e3-4432-b301-d9df28ceaeb4.png)
When you click show me how on the notification it should change to an input field which will only take a link in the form of a mountain project profile URL ex: https://www.mountainproject.com/user/200381859/brendan-downing
After you submit your URL the modal should disappear and not show up again unless you change the ticksImported flag in the UserMetaData to false.
![Screen Shot 2022-09-06 at 9 10 31 AM](https://user-images.githubusercontent.com/24400646/188686622-4c8a5c96-7247-4070-b870-cd1397a263d1.png)
You should be able to tick a climb by clicking the tick this climb button, have a modal pop up, and see that information persist in the staging database
![Screen Shot 2022-09-06 at 9 11 06 AM](https://user-images.githubusercontent.com/24400646/188687658-e9b48876-6016-434b-b9b5-385869626535.png)
Once you tick a climb, the button should say 'View Ticks' which will lead you nowhere currently.
![Screen Shot 2022-09-06 at 9 11 34 AM](https://user-images.githubusercontent.com/24400646/188686753-11deaf06-a849-4860-bfbb-6db70d18d814.png)
If you query the staging database by userID or userID and climbId, you should be able to see the respective ticks
![Screen Shot 2022-09-06 at 9 14 06 AM](https://user-images.githubusercontent.com/24400646/188686911-e4877836-46c2-4b55-822a-ddb6b5aca5d2.png)
If you run into any bugs, or have any suggestions for improvement please leave a comment here or message me on discord. In the coming weeks, I plan to add a standalone ticks page with some data visualizations that can be accessed through the user profile, and from a climb page if you have ticked that climb previously.
The text was updated successfully, but these errors were encountered: