Skip to content

Instantly share code, notes, and snippets.

@donaldpminer
Last active August 29, 2015 14:27
Show Gist options
  • Save donaldpminer/f9d80921984c67dbaae9 to your computer and use it in GitHub Desktop.
Save donaldpminer/f9d80921984c67dbaae9 to your computer and use it in GitHub Desktop.
EDHREC Current Issues and To Do List
These are the list of known issues for edhrec.com
Recommendations are recommending cards that are within color identity but shouldn't be in the deck-- like fetchlands of colors that souldn't be there.
This fix is moderate in complexity and is of high priority.
Deckstats being able to pull recommendationsf or their web interface is no longer working.
I need to recreate the endpoint that was serving up the recommendations to them.
This fix is moderate in complexity and is of high priority.
Generate Deck feature doesn't take into account the newness of cards like other portions of EDHREC.
This makes it that new cards that are popular in decks don't show up.
The fix is moderate in complexity and is of moderate priority.
Double face cards, split cards, fuse cards, etc. don't get looked up properly.
This makes it so their images don't show up properly, their prices are not looked up correctly, and other issues.
The fix is high in complexity because of all the places I need to add special handling for this case.
This problem is of moderate priority.
Cards with the merged "AE" (as in AEther) in them are not being normalized correctly.
This makes it so they aren't included in recommendations and they also don't show up properly, and other issues.
The fix is high in complexity because I need to overhawl how I'm handling text in general to fix this properly.
This problem is of moderate priority.
The quotes in Kongming, "Sleeping Dragon" screw up all kinds of text in the web front end because of the quotes.
In order to get around this, I basically pretend Kongming doesn't exist currently.
The fix for this is to add special cases for Kongming to ignore the double quotes.
I could escape quotes in all cards, but this would significantly add to CPU utilization just for this one corner case.
This problem is of low priority.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment