You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This should be structured very similarly to schedule groups, we need to support franchise groups that contain franchises (franchise holds the join column), as well as parent groups (child holds the parent id).
This will allow us to implement the Division / Conference pattern that is used by MLE.
This issue includes only the models and bootstrapping (entities, seeds, repositories for the database | objects, resolvers for GraphQL). Implementation can be followed up on.
The seeds should create the following:
2 Franchise Group Types (Conference and Division)
1 Conference
2 Divisions (Backyard and Pond)
These divisions should belong to the conference
The text was updated successfully, but these errors were encountered:
This should be structured very similarly to schedule groups, we need to support franchise groups that contain franchises (franchise holds the join column), as well as parent groups (child holds the parent id).
This will allow us to implement the Division / Conference pattern that is used by MLE.
This issue includes only the models and bootstrapping (entities, seeds, repositories for the database | objects, resolvers for GraphQL). Implementation can be followed up on.
The seeds should create the following:
2 Franchise Group Types (
Conference
andDivision
)1 Conference
2 Divisions (
Backyard
andPond
)The text was updated successfully, but these errors were encountered: