--- tags: Dungeon Master --- # Dungeon Master v1.5 scope ### [TASK BOARD ON JP's NOTION](https://www.notion.so/jonathanprozzi/d487183555d34f1caab5f8cf351cd91c?v=d25478743ca24a0c8feb7a13024cf88b) ## API / Migration - Get data into Hasura API/DB - Minor extensions to data model - Inline optimizations to views - Streamline with updated patterns ## Frontend - [x] Raider Detail/Profile - [x] Show Raids participated on - Active and historical - [x] Improved ability to update Raider detail data - Show all data that is there and then certain fields may be read only - `isRaiding` -- this is a signal for folks who are looking for work - [x] Raid Detail/Profile - [x] Improved ability to update Raid detail data - Anyone in the Party? This may be part of the permissioning - [x] [Stretch] Signal interested in this raid(?) - [x] Signal button - [x] Surface to Raid's Cleric to see list of folks who are interested -- - [x] Raid List/Cards - [x] show members in raid party - [x] show any roles required - [x] show most recent comment - [x] adjust menu order (ship/lost/all at bottom) - [x] reframe comments as an update feed (like Linear) - [x] On hover: show truncated version of the most recent update - [x] Avatar hover could surface key information -- being able to get the full context of the last comment on click, but surfacing as much as possible on hover would help with identifying things - [x] Sorting by various metadata: - [x] Oldest comment on active Raid (default) - [x] Recently commented - [x] Recently updated - [x] Member list - [x] Default sort could be name -- searching for folks - [x] Switch to show *only active* (`isRaiding` is true) - [x] Permissioning v1 - [x] Unauthenticated Display - [x] Cleric & raid party can edit raid - [x] Cohort is mostly read (can signal) - [x] Raider can edit own profile - [x] Data Fetching: - [x] Integrate pagination and switch to React Query structure for more streamlined and efficient data fetching - [x] Switch mutations to use Hasura and React Query - [x] Add loading and error states for each query - [x] Invalidate queries based on mutations - [x] Integrate infinite scroll to improve UX with data fetching - [x] Chore: Switch to RainbowKit/wagmi for handling wallet connection - [x] Chore: Version upgrades - [ ] Chore: Improve type safety -- switch to stricter TypeScript rules with new API integration - [x] Chore: Use `design-system` - [x] [Stretch] Search - [x] Multi-object search (fuzzy search) - Goal is for this to be top-level ## Notes / Scratchpad @scottrepreneur -- do we want to include any of the ideas we had around surfacing comments to the main feed in a modal? Or being able to sort by more metadata such as 'most recently updated' or do we want to hold off until we have a more defined idea of the requirements coming out of the Travii research work?