search

hiebj / stately

elegant, type-safe state management
2 stars 1 forks source link

create linter rule(s) to catch expected errors when possible #5

Closed hiebj closed 5 years ago

hiebj commented 5 years ago

There are several known conditions that will cause problems for the user. For example, calling asyncLifecycle() with an anonymous function means that stately cannot infer a human-readable "infix" for the action type string. These conditions should be reviewed, and a linter rule should complain to the user whenever possible. (the above should certainly be possible)

hiebj commented 5 years ago

This is probably overkill. Can always reference or reopen this issue later.