We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Fixed formatting on Implementation Steps
Fixed confusing typo
Made one bit a bit more precise
Add a note about dynamic state for components needing to be stored somewhere in the State object
Mention the tasklist that applies moves on the server
Add a ref to Go Implementation Scratch
Describe notion of single stack
Briefly describe Colors
Enumerate the types of State Properties that are allowed
Describe asset manager.
Add a notion of NamedStackCollections.
Define the notion of Cap for stacks, and FixedLengthSTacks
Explained a bit more about why having individual DRAW_CARD moves is a good idea.
Developed the notion of santiy checking in proposed moves to make sure the state didn't change from underneath them.
Describe a notion of derived properties
Descfribed a bit about UserGroup ACL
Added a step to implementation plan about logic engine
Add a note about sets and items
Added a TODO about virtual properties
Add TODO about stacks and caps
Added notes on what are next steps
Updated Overall Design (markdown)
Add tODO noting that moves need santized fields too
Add a TODO About if we need nested properties
Add a link to the scratchpad about optimistic moves
Some thoughts on some UI patterns of optimistic application of moves
some explorations of applying moves locally
Some exploration of how to do animations
A bit about using Web components
A few thoughts about where move logic lives