You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2021. It is now read-only.
I'm happy to implement this feature myself but I wanted to get feedback on how well you think it fits into your roadmap for the application. There are often cases where I've made a misplay, and it's apparent either on that turn, or after the game is over. Any tracking of this would have to be entirely manual, but it'd be nice to input them, and then at the end of the day review the misplays that I've made so I can learn from them. It'd serve a similar function to a leak tracker in poker.
For this, we'd probably need to add a "matches#show" and "matches#edit" route. While this would add some slightly heavy feeling pages to the currently light UX, I think that future feature development will necessitate the addition of those regardless.
(As a side note, I'm the maintainer of Active Record and I'd love to submit a few PRs to clean up the models if you'd be open to that.)
The text was updated successfully, but these errors were encountered:
Maybe a generic tagging system combined with some filtering mechanisms could be used to implement the functionality you suggest. It would allow users to separate and classify their matches in the ways that they find useful.
Hi there,
I'm happy to implement this feature myself but I wanted to get feedback on how well you think it fits into your roadmap for the application. There are often cases where I've made a misplay, and it's apparent either on that turn, or after the game is over. Any tracking of this would have to be entirely manual, but it'd be nice to input them, and then at the end of the day review the misplays that I've made so I can learn from them. It'd serve a similar function to a leak tracker in poker.
For this, we'd probably need to add a
"matches#show"
and"matches#edit"
route. While this would add some slightly heavy feeling pages to the currently light UX, I think that future feature development will necessitate the addition of those regardless.(As a side note, I'm the maintainer of Active Record and I'd love to submit a few PRs to clean up the models if you'd be open to that.)
The text was updated successfully, but these errors were encountered: