Machine best practices
-
Name your actions and declare them in setup with their implementation
-
Organize your files in a structure like the following name (permissions, application lifecycle, etc) ├── .machine.ts ├── .types.ts ├── .actions.ts ├── .actors.ts
-
Should we have every actor declared in a system???
- PROS
- system.get works
- everything is explicit
- you can simulate everything in that actor system headlessly
- CONS
- Complexity...
- Should we use emit? I don't think so, because it causes implicit dependencies at the cost of convenience