There are some repeated model classes/interfaces throughout the front end and we should review these to try to consolidate them as much as possible. For example, There are Stage interfaces defined in both StandingsData.ts as well as PairingsData.ts - can we have a single Stage interface that is used everywhere?
Additionally, we should review the current organization of models, request methods, and utility methods to see if there's a more consistent way of organizing these. Some Svelte components outside of the app/frontend/pairings directory use elements from app/frontend/pairings/PairingsData.ts. There are many such bespoke .ts files - is there a better way to organize these for consistent use across the app?
There are some repeated model classes/interfaces throughout the front end and we should review these to try to consolidate them as much as possible. For example, There are
Stageinterfaces defined in both StandingsData.ts as well as PairingsData.ts - can we have a singleStageinterface that is used everywhere?Additionally, we should review the current organization of models, request methods, and utility methods to see if there's a more consistent way of organizing these. Some Svelte components outside of the app/frontend/pairings directory use elements from app/frontend/pairings/PairingsData.ts. There are many such bespoke .ts files - is there a better way to organize these for consistent use across the app?