Devlog
A funny story: I built the invoice system but didn’t always assign values correctly, so the values got mixed up. I spent a long time debugging before realizing that was the cause.
{
"error": {
"message": "VALUE_ERROR",
"description": "\"Car\" object has no field \"123\""
}
}
I also spent a lot of time on CSS. Most of that time went into learning:
- classes
- IDs
- box shadows
- CSS Grid
The reason it took so long since the last devlog is CSS. As I said before, I don’t really like web development, so my motivation was pretty low.
I used some AI, but I worked hard to remove most of the generated code. At this point, most of the site’s design looks the way I want it to and will probably stay that way until the end of the project.
Made invoices have some logic instead of always sending the same value.
That means:
- If no invoice status is set, it sends
COMPLETEDorRUNNINGdepending on whether the engine or climate is running. - Loc like actions can’t have a
RUNNINGinvoice status. - Added a distinction between successful and failed invoices.
PS: Always remember to stop the server with Ctrl+C, not Ctrl+Z, because Ctrl+Z can leave the process running and keep the port blocked.
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.