-
Loading React Component by Convention
Next.js uses file-system based routing, meaning you can use folders and files to define routes. Basically, you don’t need to define routes, and if you access the app by a folder and file path, you can get the component. React Router can also do this. Instead of doing the following:
-
A helper funciton to render nested multiple components
From time to time, we need to render nested multiple components in React.
-
A helper function to quickly provide service in react
In Angular, we can inject services into components so that components can share state and communicate with each other. In React, we can use context to provide services to components too. Here is some sample code.
-
Anti-patterns of NgRx
Mike Ryan is one of the authors of NgRx. He has a YouTube video “You might not need NgRx”, which showcases when you can use NgRx. Some people just don’t care about those use cases and use it in the wrong scenarios, writing unnecessarily complex code, which makes others hate NgRx more. While it is important to document when to use it, and how to use it, it is equally important to document when you should not use it. In this post, I am trying to document some of the anti-patterns in using NgRx.
-
Rethink NgRx - A more complex example(part 3)
In the counter example, action and reducer is one to one mapping. It does not show the flexibility of decoupling action and reducer. I need to use a more complex example to showcase that. In the following, I will build sales app with store. Here is the features of the app. After login, the app will load your recent orders and you preferences, and you can logout from there. After login, the session will timeout and logout if screen is idle for 10 seconds. If you move your mouse, session will be renewed. After session timeout or user logout manually, the session tracking will be turn off.