Release Notes v0.7

Table of Contents

1. User Account and Authentication
   1. Updated Profile, Sign In, Sign Up, and related functions for AWS Amplify v6
   2. Modified user preference settings and database structure
   3. Core application upgrade to AWS Amplify v6
2. Application Programming Interface
   1. API upgrade to 1.0.8 with enhancements to user preferences
   2. API upgrade to 1.0.9 for dependency upgrades
   3. Optimized deck search queries and results
3. Deck Technology
   1. Organized cards being displayed in both gallery and list views
   2. Modifications to import and export cards feature
   3. Full Decklists allow continuous decks with load more button
   4. Deck page data load feature updated
4. Search Pages
   1. Enhanced card search page functionality
5. Development Roadmap
   1. Incorporate cubes and card collections
   2. Import / export deck enhancements
   3. Implement new safeguard when deleting decks
   4. Deck views and likes
   5. Expand user account information
   6. Commander and new format enhancements
   7. Add public and private User pages
6. Known Issues
   1. Server Data for Deck pages
   2. Issue editing deck tags on mobile
   3. Mobile homepage load issue
   4. WebPack warning from MongoDB and React upgrade
   5. Card prices not loading

1. User Account and Authentication

a. Updated Profile, Sign In, Sign Up, and related functions for AWS Amplify v6

The core structure of AWS Amplify authentication was rewritten to match syntax in v6. All related components, functions, and classes associated to the Profile, Edit Profile, Sign In, Sign Up, Verify, and Delete pages were upgraded.

b. Modified user preference settings and database structure

User preferences structure and visual displays were updated for the upgrade to AWS Amplify v6.

c. Core application upgrade to AWS Amplify v6

Dependencies, classes, and functions associated to users, user preferences, and authentication were upgraded.

2. Application Programming Interface

a. API upgrade to 1.0.8 with enhancements to user preferences

The Deckster API was updated to accommodate the new database tables for users and enhancements for saving and deleting processes for decks and users.

b. API upgrade to 1.0.9 for dependency upgrades

The Deckster API was updated with core node package dependency upgrades to axios, express, mongodb, and mongoose.

c. Optimized deck search queries and results

Deck search queries and responses accurately depict the current options and were fine tuned to be more inclusive of all options selected.

3. Deck Technology

a. Organized cards being displayed in both gallery and list views

Cleaned up visual display issues with cards in the correct categories and optimized the gallery and list view styles.

b. Modifications to import and export cards feature

Updated the process of parsing card data to import the list into either mainboard or sideboard.

c. Full Decklists allow continuous decks with load more button

Decklists on the default homepage and logged in homepage that allows the user to load more decks for viewing in batches of six decks until all decks have been loaded.

d. Deck page data load feature updated

The current deck page structure was updated to accurately load information, but is undergoing a full overhaul to better produce server-side rendered content for social media feeds and search engine optimization.

4. Search Pages

a. Enhanced card and deck search pages functionality

Warnings and form structure was updated for ADA compliance and style revisions for a better user experience and abillity to begin adding more searchable feature fields.

5. Development Roadmap

a. Incorporate cubes and card collections

The plan will be to incorporate a non validated card template for a new List feature that may be designated as a Card Collection or Cube. The Card Collection will be a private or public collection of cards. If a List is marked as a Cube will be accessible with other decks built in searches if made public.

b. Import / export decks

Deeper testing and development of ways to include import and export features for ease-of-use with other applications and tools. Connec the import deck feature to decifer the sideboard and begin importing there.

c. Implement new safeguard when deleting decks

When deleting a deck, there will be a safeguard added to type the word DELETE before the user can successfully delete the deck.

d. Deck views and likes

User engagement will slowly be added to the application. The first wave will include deck voting and total views of publicly accessible decks.

e. Expand user account information

The addition of more fields for user information will be added to the Profile and Edit Profile pages. This allows us to introduce more user engagement tools in the future.

f. Commander and new format enhancements

Look into including game changers and assigning a deck to a specific play category. Review all other formats and see what will need to be included and/or improved.

g. Add public and private User pages

Incorporate an optional public profile page with your chosen information saved in user preferences.

6. Known Issues

a. Server Data for Deck pages

The getServerData function is not correlating with the current system and returns serverData as undefined. We're working on properly addressing this issue to solve the deck page load issues when sharing or crawling the dynamic page.

b. Issue editing deck tags on mobile

Currently the tools assisting in the user interface for tags on Deck pages is not working on mobile. They can be seen and removed, but not added. Styles, targeting, and slight reworking of the fields is needed in order ot correct the issue.

c. Mobile homepage load issue

Occassionally a user will try on a mobile device to go back a page and when attempting to load the standard homepage after logging in, the app stalls on loading either the original homepage or the user's logged in homepage. This will be addressed in a future patch.

d. WebPack warning from MongoDB and React upgrade

After upgrading all necessary node packages, serveral conflicts are causing WebPack to kickback warnings for serializing big strings. It may be associated with the upgraded version of React (19.x) and MongoDB. An error shows as well during the build process but does not affect the output of pages for within the GraphQL. We will either be rolling back React if no other patch can be found.

e. Card prices not loading

Not all versions of cards seem to be retrieving a price from TCG even when the cards are available for sale with average near mint and foil prices. They are supposed to show either one or both depending if the card exists with an average price. This will be addressed and will also patch total deck values that are lacking these card values.