question: enumerable event properties

[boneskull]

I'm curious why "event" properties are enumerable when other properties (such as can and cannot) are not?

[vstirbu]

The idea at the time was that the public api surface of the fem object is just the events set, the rest would be private. The private api was used for testing or just compatibility with the inspiration.

[boneskull]

is it still necessary to have them either way?

[vstirbu]

They can be made enumerable and in addition the lib should throw an error if the state machine definition contains any event names that would conflict with the library added methods: is, can, cannot and current.