The BURG has enough information to generate a reducer interface; this would help identify the required changes to the reducer when rules are added or changed.
The driving use case (a common set of patterns and two reducers) turned out to create sufficiently disjoint reducers that this is no longer considered to be much of a good thing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would also be good to have a way to include enums in this interface.
The driving use case (a common set of patterns and two reducers) turned out to create sufficiently disjoint reducers that this is no longer considered to be much of a good thing.
Reopened to support separation of concerns in large-scale projects.