JECS can automatically parse enum types but if you want to add a custom parser for one the default behavior is called before any registered custom base type logic.
This becomes less of a problem once #32 is resolved as the most obvious use case currently is for implementing that logic on the user end (this is how I discovered this limitation) however it is still possible others may have a use for custom parsers.