Say I have a React component -- dumb or not -- and I want to grab something from the store and put it in a variable to make my code a bit more terse. Should I use const or let? Clearly the state will change.
Here's an example of what I'm talking about. Again, I want to emphasize that myValues WILL change as user interacts with my app.
class MyComponent extends Component { render() { // Here, should I use const or let? const myValues = this.props.someData; return( <div> {myValues.map(item => ( <SomeOtherComponent key={item.id} data={item} /> ))} </div> ); }; } function mapStateToProps(state) { return { someData: state.someValuesComingFromApi } } export default connect(mapStateToProps)(MyComponent)
const is short for contant, which indicates the variable's value won't change.
To declare a constant that can be accessed in a React class component, there are multiple approaches that could be efficiently implemented such that constant is accessible class-wide. Constants can be declared in the following two ways: Create a getter method in the class for getting the constant when required.
let is the block scoped version of var , and is limited to the block (or expression) where it is defined. If you use let inside of a block, i.e. a for loop, the variable is only available inside of that loop. let has a block scope.
Embedding Expressions in JSXconst name = 'Josh Perez';const element = <h1>Hello, {name}</h1>; You can put any valid JavaScript expression inside the curly braces in JSX. For example, 2 + 2 , user. firstName , or formatName(user) are all valid JavaScript expressions.
const
is a signal that the variable won’t be reassigned.
let
is a signal that the variable may be reassigned
Additional things to ponder:
const
by defaultlet
only if rebinding is neededconst
does not indicate that a value is ‘constant’ or immutable.
const foo = {}; foo.bar = 10; console.log(foo.bar); // --> 10
Only the binding is immutable. ie using an assignment operator or a unary or postfix -- or ++ operator on a const variable throws a TypeError exception
ES6 const
and let
are hoisted too. Although the identifiers has the same memory reference from compile time, they cannot be accessed before declaration in the code. (but not as we thought the declaration would be physically moved to the top in the scope) ;)
const
vs let
is mostly to do with "changing" in a code block. It only matters in situations like this:
const myValues = this.props.someData; if (*some condition*) { myValues = []; }
In this situation you would need to use let because you are changing the value assigned to the variable myValues
:
let myValues = this.props.someData; if (*some condition*) { myValues = []; }
If props.someData
is changing it will trigger a re-render of the component. So const vs let does not come in to play. The entire render
method is re-run.
So that said, I use const
in the situations you are describing. Unless you are directly manipulating the valuable of a variable, use const
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With