Is it true that for both React or Angular, they are also both "convention over configuration"?

Question

In the Ruby on Rails communication, it is often said that RoR is "convention over configuration".

Can you say for React / Redux / Flux and AngularJS, Angular2, they are also "convention over configuration"?

---

Some details: the reason is, engineers probably do things in quite standard, or convention ways, such as

// in index.js:

const createStoreWithMiddleware = applyMiddleware(ReduxPromise)(createStore);

<Provider store={createStoreWithMiddleware(reducers)}>
  <App />
</Provider>

// in the container file:

function mapStateToProps(state) {
  return {
    dataList: state.data
  }
}

export default connect(mapStateToProps)(DataList);

and you usually won't tweak or change these conventions. (I just hope no interviewers will ask me to recite these lines verbatim at interviews... as whether you memorize these lines, do they make you a better programmer? The concepts can be important, but how these lines are verbatim, what is so good about memorizing them?)

Answer 1

No, you've misunderstood convention over configuration.

The idea of convention over configuration is that you should not have to explicitly configure the framework. Instead, conventions are automatically applied.

Take for example:

export default connect(mapStateToProps)(DataList);

React makes you explicitly include this code. If React followed convention over configuration, it would assume that you wanted to do this as soon as you defined a mapStateToProps function and automatically do it for you.

So the point isn't that there is a standard convention. Convention over configuration is when the convention is automatic, not explicit in code.