Document actionType exports

[griffinmichl]

I find myself using the exported action types somewhat regularly when I combine redux-form with redux-observable or redux-saga. For example, if I want to hook into onChange actions to run async validation through a saga / epic as the user types. Sharing actions b/w reducers is also a powerful aspect of the redux architecture.

I think adding the exported actionTypes to the docs would expose people to all the possibilities this library offers.

I'd be happy to contribute this addition if it sounds worthwhile.

[gustavohenke]

Sure, go ahead!

What are your ideas on how to document this?

[griffinmichl]

I was thinking a sidebar section that looks pretty similar to the action creators section and briefly explains why the actions are exported at the top.

I'd also add an example to the FAQ of using exported actions types to do something fancy that isn't supported natively by redux-form. I found the 'submitting a form with websockets' FAQ example super helpful as I figured out how to make redux-observable play well with redux-form, and I think more examples of just how much you can do w/ this library would be very cool.

Examples might be onChange async validation or providing feedback to the user as inputs come in (one project I'm working on requests and displays estimates of an advertiser's audience size via an epic as they input their targeting parameters into the form).

[gustavohenke]

Because this issue saw almost no activity for a few months, I'm closing it.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.