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

Add an autosplitter badge #674

Merged
merged 3 commits into from
Feb 10, 2020
Merged

Add an autosplitter badge #674

merged 3 commits into from
Feb 10, 2020

Conversation

glacials
Copy link
Owner

@glacials glacials commented Feb 7, 2020

Adds a badge to runs that were performed using an autosplitter:

Screen Shot 2020-02-07 at 13 04 30

I had trouble with the tooltip even after hard loads, so I dove a bit into solving them globally -- now that our whole site is in a Vue app container, even if we're not using Vue in a given place we can still take advantage of the Vue tippy tooltips, which show consistently regardless of soft/hard loads, so I moved the surrounding tooltips over to that style.

Adds a badge to runs that were performed using an autosplitter.
@CryZe
Copy link
Contributor

CryZe commented Feb 7, 2020

I believe using the auto splitter settings is potentially going to cause false positives and false negatives. You may reuse the same splits for a different game and the settings might not get cleared out. And you may use an auto splitter that doesn't have settings.

@glacials
Copy link
Owner Author

glacials commented Feb 8, 2020

Hm, is there any better way of detecting autosplitters?

@CryZe
Copy link
Contributor

CryZe commented Feb 8, 2020

Not really. But detecting the auto splitter settings should work in a lot of cases.

href=run_path(run, params.permit(:compare).merge(timing: 'game'))
v-tippy=true
:title='"Recorded in realtime & gametime—click to switch"'
Copy link
Collaborator

Choose a reason for hiding this comment

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

I believe if you don't put the colon before the attribute you won't have to double wrap the strings. From my understanding the colon tells view to interpret it as JS first.

Copy link
Owner Author

Choose a reason for hiding this comment

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

Could have sworn title was a special case with this, but now that I try it it works fine and I can't find anything in the docs about it not working. ¯_(ツ)_/¯

@glacials
Copy link
Owner Author

glacials commented Feb 9, 2020

@CryZe Alright, I'll go ahead and merge this and accept that there will be some false positives/negatives. Seems like the common case should be fine, but I'll keep an ear out and remove if it's causing too much confusion. Thanks for the input!

@glacials glacials merged commit f3cd4b0 into master Feb 10, 2020
@glacials glacials deleted the autosplitter_badge branch February 10, 2020 00:52
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