Closed JonathanMerklin closed 4 years ago
Hi Jonathan,
Thanks for your consideration and for taking the time to logs this issue. Currently, we don't support React hooks with building NR1 apps, but we have this update on our roadmap and once complete the workshop will get an update.
Thanks!
Mostly bikeshedding, not an "issue" per se, but I noticed that despite the fact that you're leveraging
"react": "^16.6.3"
, you've written a bunch of class-based components throughout this tutorial and using the "classic" component lifecycle, which is fine and perhaps an intentional decision for legacy clients that are more used to it (I know my current org is maintaining a mix of React 0.x/15.x/16.x).But it may be worth considering that as the "canonical way to write React" gradually shifts towards hooks and the like, it may be worth updating the tutorial as well, lest it appear dated and ward off your potential customers.
As a simple example translation, I don't think I see any reason why the lab1
The resulting index.js should look like the following:
can't be (moduloexport default
->export
to permit the arrow function and not a class)(as opposed to what it is as of this date i.e.)
Again, mostly bikeshedding, but I figured I'd raise the issue. If this is intentional and there is a technical reason for using the lifecycle methods, feel free to close! :)