This is the pattern I currently use!
[action](_[additional_identifier])_[namespace]_[what happened]
e.g.
CREATE_TOUR_REQUEST
CREATE_GROUPS_TOUR_REQUEST
GET*_PROJECT_REQUEST
UPDATE_PROJECT_REQUEST
DELETE_PROJECT_REQUEST
CREATE**_PROJECT_REQUEST
*using get
as it refers to an async http request (to me), whereas 'read' feels more like a synchronous action. So following crud except for 'read'.
**using create
instead of add
as I feel create is a stronger idea about creating something new. Add is a good alternative for when something that exists is being added to something.
What resource this is under.
Something additional needed to identify.
e.g.
CREATE_GROUPS_TOUR_REQUEST
This is for when an action is indicating what part of a thunk action it is at.
There's three main states, but the naming is flexible for more. I don't know why, but I like "failed" more than "fail" even though the other terms aren't past tense.
[action]_[namespace]_REQUEST
[action]_[namespace]_SUCCESS
[action]_[namespace]_FAILED
Same as the Actions except with camelCase:
getTourRequest
Same as Action Creators, except without the last word:
getTour