| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
Instead of repeatedly supplying Card content in all the places it is
required, it makes more sense to create dedicated ComicCard and
ArchiveCard components. These wrap around Card itself and can be used in
a more straightforward and consistent fashion.
Whilst we are here, simplify and streamline the display of Comic and
Archive metadata by introducing a Card footer. The footer is used for
information on page count, release date, and archive size.
|
| |
|
|
|
| |
Now that we have all association counts mapped to their respective
models we can easily allow sorting on them as well.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will replace the old 'empty' filter on comic associations and
introduce a generic way of matching against association counts, along
with support for different operators like 'greater than' or 'lower
than'.
Models that did not previously have a way of matching against their
associates (like filtering for Artists that have N comics associated
with them) now gain that functionality.
For now the frontend keeps the simpler approach of allowing the user to
only filter for empty associations, but we nonetheless need to adjust
the 'empty' field to instead be linked to the new 'count' field.
|
| |
|
|
|
|
|
|
|
|
| |
Use the current date (year, month, and day) instead of generating a new
seed every time and potentially making the user unable to go back to see
results that were displayed a moment ago. This essentially makes the
frontpage display daily favourites and bookmarks.
Additionally make sure to set the seed in the filter when navigating to
the respective category.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
GraphQL integers are 32-bit as per spec [1] [2]. Implementations may
therefore error on large numbers. Since an archive's size can reasonably
exceed this value, make sure to report it as a float instead.
[1] https://graphql.org/learn/schema/
[2] https://github.com/graphql/graphql-js/issues/292#issuecomment-186702763
|
| |
|
