bday-boy/weeble

Uses anime data from public APIs to create a guessing-based, Wordle-like anime game.

weeble's Issues

Quitting Safari resets daily

It looks like quitting Safari (on iPhone, at least) clears the browser's cookies, but NOT the local storage data, so the user's daily and their daily guesses are deleted. Guesses should be stored in local storage instead so it remains persistent. This is probably preferable anyway because the daily cookie is set to delete after 24 hours whereas storing guesses in local storage will remain forever. This means the user could potentially check their guesses from any day in the past (if I decide to implement something that allows for this down the line).

Title collisions

When two anime have the same title and are searched for, only one will show up in the suggestions. This is a back-end issue as each title should be unique in the anime json.

LCS unexpected behavior

With fuzzy string search implemented, the user's search often functions oddly. For example, when the user searches "Saiki K" in hopes of getting "The Disastrous Life of Saiki K." to show up in the suggestions, it instead shows up as "The Disastrous Life of Saiki K." and this causes it to become a lower-priority search.

X close button hard to see on light mode

The "X" button on modals is very light and difficult to see on light mode.

Make all requests to AniList local resources

Posting a GraphQL request to AniList literally takes like 5 seconds. So just keep all AniList requests on the website itself instead