React, Loki and XState
Motivation described here: https://theredcircuit.com/posts/reactLokiXstate/
Component descriptions here: https://theredcircuit.com/posts/reactLokiXstatePart2/
I intend to write a part 3 to discuss the XState machine used for the form. https://theredcircuit.com/posts/reactLokiXstatePart3/
Questions
- Why do you have
rc()(short forreact.createElement()) calls instead of JSX?- At my work we have a VERY large component code base and running JSX babel transforms was taking up the vast majority of the time needed to run our unit tests. This syntax is almost identical to JSX, but without the need to do context switching with curly braces whenever you need code or a variable value. It's all JavaScript.
- Why do you always declare functions on your react exports?
- Because then the component or hook name will appear in stack traces (or the inspector Component tree) instead of
__WEBPACK_DEFAULT_EXPORT__.- For example
export default function useLokiView() { /* hook code */ }will give the function name in the stack asuseLokiView, whereasexport default ()=>{ /* hook code */ }will give it as__WEBPACK_DEFAULT_EXPORT__.
- For example
- Because then the component or hook name will appear in stack traces (or the inspector Component tree) instead of