Static feature modules, a root options module and token overrides in createApp #425
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#426 One clock for the whole API, injected and overridden once
amaurycoudr/chess-project
#427 The account/ layer: one Account controller for account.me, account.export and account.delete
amaurycoudr/chess-project
#424 Guest as plain functions: no GuestService, no global Guest module, the oRPC module imported once
amaurycoudr/chess-project
Reference
amaurycoudr/chess-project#425
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#421
What to build
Feature modules declare their dependencies, configuration enters the app in one place, and tests replace providers by token instead of through production options.
createApptakes an optional second argument, a list of{ token, value }pairs applied as provider overrides before the app boots.connect()passes overrides there. Tests that passed per-feature options (Rooms, Auth, Games, Guests) override the option tokens instead.Room's factories that turn Games into its
isClaimedandonDecidedcallbacks stay as they are. No configured module object is passed from one module to another.Seam: S1, the wire through the real app.
Acceptance criteria
forRootreceives another module.createAppapplies token overrides before boot.connect()uses them for the sweep scheduler, the hash cost and every former per-feature option.mentioned in issue #426
mentioned in issue #427
marked this issue as related to #421
marked this issue as related to #424
marked this issue as related to #426
marked this issue as related to #427
mentioned in commit
a8af303289mentioned in merge request !536
mentioned in commit
6a3a6992eementioned in commit
215cdba4c9mentioned in merge request !537