Rename `send` to `action` in docs & examples?

Saw a lot of work is going on with v4. Very cool!

Just a thought here – actions are mentioned a lot as a concept throughout the documentation, but don’t exist as a word anywhere in the examples. What if we renamed send to action, since that’s what it’s doing? e.g.

const mainView = (state, prev, action) => html`
  <main>
    <h1>Title: ${state.title}</h1>
    <input
      type="text"
      oninput=${(e) => action('update', e.target.value)}>
  </main>
`

This might help clarify concepts and bring the ideas from the unidirectional architecture chart into the code – making it easier for beginners to understand and pick up. Since send is always referenced as a parameter it would not change the API at all, just the examples, and I think it would solidify the relationship between concepts and code considerably with one small tweak.

[yoshuawuyts]

@timwis that would break the unidirectional model, and would require the extra done() callback in the views. I think creating a clear boundry between views and logic so far has paid off, I’d be cautious to mess with that

[Ryuno-Ki]

In this case maybe updating the docs with “An action can trigger either an effect or a reducer.”?