Basically my school uses hong chiao's systems which has a lot of apis and questionable design choices, and the main thing, a bad web UI. This project uses Next.js as the backend and just forwards the cookies and requests to the website.
I have been hinting on the new AI chat bot features, with including the new tRPC migrations with batch APIs, and with a new fancy graph (hint hint, its included). And bringing more and new interfaces to this unpleasant system.
The main thing here is of course the fancy new AI chat features, in this time, I built a basic AI chat setting, a basic popover chat app thingy, and adding a new random graph lib I found on Twitter.
This change included a new change into the core backend API system, instead of using the Next.js App routing, I moved to tRPC for better and faster development, this changes are partly done by Codex. This change also brought more UX changes, including prefill usernames (on login with param ?prefill=true), better password changing, tuition fetching, and tuition discount forums. All of this without using a server side db. Later, some stuff will have error handling, currently, there is none. Like the tuition discount forums.
Worked on the main leave component, with a kinda broken displaying history system, but the main creation system works properly with faster and much more easier to interact web UI and API. With a new dashboard, and a empty info page. With a new account password reset flow at the account page, which I got an account from a friend and tested the account changing “requirement”, which is just a popup, and its not required to use the platform, so a new toast that just tells the user to change the password.
Add new password expiry notice. This change also includes quick access better summaries. And a few TBD features for the leave section of the app, including uploading & downloading files. with actual name fetching instead of just getting the thing from your user id.
Worked on some API endpoints and the login/dashboard page. Before recording this devlog, the captcha error got patched and the server admins added ASP.NET request verification, which is patched quickly with a quick input component.
