adipginting/industrialisasi-ui

The User interface of Industrialisasi CMS

• 👋 Hi, I’m @adipginting
• 👀 I’m interested in the world wide web, software engineering, statistical physics, machine learning, and the human side of technology.
• 🌱 I’m currently focusing the javascript ecosystem (Node.js, React.js, Express.js, Next.js, Nest.js & TypeScript) and learning OpenAPI, Docker, and Database (PostgreSQL & MongoDB) on the side.
• 🚀 This year, I am focusing in JS/TS, Python, Java, and Golang.
• 💞️ I’m looking to collaborate on building website and distributed systems.
• 📫 You can reach me here or if you want on Twitter @adipginting.

industrialisasi-ui's Issues

Posts do not show on the main page

Posts do not show on the main page. The API call to the /posts end point of the restful server seems to be missing.

Can't login

The issue could be in front end or backend, but I'll make the issue here.

Convert React UseEffect on Register.js to useQuery

The useEffects make the code quite unreadable. Convert it to useQuery.

Can't send email during register

Error message on browser console:
XHRPOST https://api.industrialisasi.site/sendemail [HTTP/1.1 404 Not Found 32ms]
Most likely an error caused by changing in the route of /sendemail.

Refactor code to achieve good separation of concerns

To be maintainable, code needs to have a good separation of concerns[0]. The issue with this repository is that it needs separation of concerns. Separate user interface, input validation, API query, etc [0].

Reference:
[0] https://twitter.com/effendii_/status/1636776359237398530

Refactor code to use less useEffect Hook (especially useEffect chaining)

Too many useEffect hooks can make code to be unreadable and hard to maintain[0]. It is better to refactor code to run sequentially[1].

References:
[0] https://twitter.com/effendii_/status/1636777024558862336
[1] https://twitter.com/effendii_/status/1636777708410793984

Refactor code that it does not need to check user login in many places

Minimize the need of code that perform checking whether the user is logged-in[0]. Some potential solutions are to use useAuth custom hook to check token in localStorage[0] putting it inside a wrapper component before router component [1] and to use AuthProvider to inject isAuthenticated value to routes that are protected[2].

References:
[0] https://twitter.com/effendii_/status/1636778330254114816
[1] https://twitter.com/effendii_/status/1636778755875311617
[2] https://twitter.com/effendii_/status/1636779181077065729