Provinite / Provinite/chardb

Species-based character filtering and dedicated species characters route

Open
#82 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
2h 52m
Merged PRs (30d)
85

Description

Problem

Character filtering by species is currently not working properly. Additionally, we need a dedicated route for viewing all characters of a specific species.

Current Issues

  1. Broken Species Filter: The species filter on character browse pages doesn't function correctly
  2. Missing Route: No dedicated route exists for viewing characters by species

Proposed Solution

Fix Species Filtering
  • Debug and fix the species filter on existing character browse pages
  • Ensure proper GraphQL query integration for species-based filtering
  • Test filter with multiple species and edge cases
Add Species Characters Route
  • Create new route: /species/:speciesId/characters
  • Display all characters of the specified species
  • Include species information header (name, description, image)
  • Apply existing character list UI patterns
  • Support pagination and sorting
  • Show empty state when no characters exist for the species

Acceptance Criteria

  • Species filter works correctly on character browse pages
  • New /species/:speciesId/characters route is accessible
  • Route displays species header with details
  • Character list shows all characters for the species
  • Pagination works if many characters exist
  • Empty state displays when no characters found
  • Proper permission checks (respect character visibility)
  • Works across different communities

Technical Considerations

  • May need to update GraphQL queries to properly handle species filtering
  • Consider using existing character list components for consistency
  • Ensure proper error handling for invalid species IDs
  • Cache invalidation after character creation/deletion

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the existing character browse pages and their GraphQL queries, then trace the species and character route entry points; no file or test names are provided. Done means species filtering works, the new route shows species details and characters with pagination, sorting, permissions, error handling, and an empty state across communities.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.