Skip to content
This repository has been archived by the owner on Oct 19, 2021. It is now read-only.

RFC: Ability to track misplays #19

Closed
sgrif opened this issue Jun 15, 2015 · 4 comments
Closed

RFC: Ability to track misplays #19

sgrif opened this issue Jun 15, 2015 · 4 comments

Comments

@sgrif
Copy link

sgrif commented Jun 15, 2015

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.)

@pencil
Copy link
Contributor

pencil commented Jun 15, 2015

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.

@stevschmid
Copy link
Owner

A generic tagging system would be lovely!

@stevschmid
Copy link
Owner

The upcoming version includes a tagging and filtering system as @pencil suggested. Hope that this helps tracking down your misplays @sgrif.

@gssjr
Copy link

gssjr commented Aug 26, 2015

@sgrif Who wouldn't love cleaner models?! :) I'd say go for it.

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

No branches or pull requests

4 participants