Yeah, so um, what’s up guys? Um, I want to show you guys how to debug your application using Charge GPT. So, I have here in front of you, uh, a dashboard more like a sales invoice dashboard that I’m currently working on using Electron JS. It’s a desktop application where you can see we have a lot of transaction history, invoices, and other details. I’m going to try and fix a bug using Charge GPT. Let me first change the token in the protected route and see if the login screen is visible. Oh, it seems like I have an error. I don’t know what the issue is, so I’m going to try and debug it. I’ll check the code and see what’s wrong. Oh, there’s no issue. I’m kind of lost right here. The only solution for me right now is to use Charge GPT and piece the problem together. I want to make sure that if the type of token is not a string, it should show the login screen. But now it’s not working as it’s supposed to. I’m going to copy the error and see if I can resolve it. Sometimes Charge GPT gives wrong answers, so you have to be careful. Going back to the code, I realized that Electron always looks for the base URL in the navigation. When there’s no authentication, the base URL is just the login component. That’s where the problem is coming from. I’m going to duplicate the logic for the routes in the authenticated and unauthenticated users. This way, Electron will have access to the router in both cases. Let’s see if everything works now. Everything seems fine except that we don’t have the router set up for the hover route. With this, everything should work fine now. Perfect!
