Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the reason action name is called "type"? #15

Closed
gajus opened this issue Aug 10, 2015 · 2 comments
Closed

What is the reason action name is called "type"? #15

gajus opened this issue Aug 10, 2015 · 2 comments
Labels

Comments

@gajus
Copy link

gajus commented Aug 10, 2015

What is the origin of a convention to call action name (e.g. ADD_NAME, REMOVE_NAME) a "type" (or "actionType" or "actionId")?

"actionId" is the most accurate of the suggested variations. However, what we are calling a "type" is actually a "name".

It is easy to see that "type" is wrong if you either lookup dictionary definition or try to replace it with either of the direct synonyms (e.g. kind, sort, variety).

@cesarandreu
Copy link

Probably legacy reasons. Facebook's flux examples use actionType.

@gajus
Copy link
Author

gajus commented Aug 10, 2015

Have a look at https://github.com/gajus/canonical-reducer-composition. It is a broader standard I have been working on. It encompasses actions and reducer definition.

On Aug 10, 2015, at 21:29, Cesar Andreu notifications@github.com wrote:

Probably legacy reasons. Facebook's flux examples use actionType.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants