gdgkirkley / readingly Goto Github PK

At the moment, the search page is set up to accept a query via URL, but it doesn't add a query to the URL itself on search. When a user navigates to a search result and then goes back, they have to search again. This would save the query when they go back and allow fetching of the already cached result.

Clicking or hitting enter on an item for a second time should deselect it and set the list back to neutral state in the AddToBookshelf component.

At the moment, the app uses an average reading speed to calculate reading times, but this should be updated to allow a user's reading speed to be the basis for that calculation. This would mean adding an area for that information to be entered on the frontend and then pulling in that information to the relevant calculations.

The mobile search bar is pretty chunky on Chrome and Safari on iOS. Likely a flex and/or padding issue.

Nav links should style as active when user is on the relevant page.

The add to bookshelf component should reset to a neutral state after adding a book to a bookshelf. This makes it easier to add to another shelf right after.

The app needs a way to define reading status (ie., currently reading, completed, etc.). This could be kept on the bookshelf level.

The user should be relatively free to choose which shelves should have which designation. The user could create a Currently Reading shelf and then give it the Currently Reading tag. This could be limited to allow just one tag to be used, or tags could be applied to multiple shelves.

A potential disadvantage to this approach is that a user has to add a book to a shelf in order to update reading status. But that is consistent with Goodreads and other services. The added flexibility of being able to designate shelves should be enough to make this better on readingly.

This will need to be added in the backend via either a new table, or an enum on the shelf. Then it will need to be added to the bookshelf features on the frontend.

When a user has many bookshelves, the bookshelf list needs to be paginated so that there are not too many items on the page and not as much data needs to be sent on initial load. 5 bookshelves per page should be perfect.

There are some resolvers that don't have integration tests yet. I'll audit the tests and add a comment with all of the resolvers that still need integration tests.