The current status component in client/components/status/status.js has grown to be very large and complex. It handles multiple responsibilities, including authentication, verification, payment, session management, captive portal logic, and UI rendering. This makes the codebase difficult to understand and maintain. The complexity also increases the risk of bugs and makes testing more difficult.
I opened this issue to gather information. We need to discuss the changes before doing any changes.
The current status component in
client/components/status/status.jshas grown to be very large and complex. It handles multiple responsibilities, including authentication, verification, payment, session management, captive portal logic, and UI rendering. This makes the codebase difficult to understand and maintain. The complexity also increases the risk of bugs and makes testing more difficult.I opened this issue to gather information. We need to discuss the changes before doing any changes.