ca610000dbb1259d3edd54f842df4614d2947f05
This commit introduces several improvements to the ESI (EVE Server Interface) Single Sign-On (SSO) flow and system name resolution: **ESI SSO Login Flow:** - **Asynchronous Callback Server:** The `StartCallbackServer` function is now deprecated in favor of `StartCallbackServerAsync`. This allows the callback server to run in the background without blocking the main application thread, improving responsiveness. - **Improved Login Status Polling:** After initiating the ESI login, the frontend now polls the `ESILoggedIn` status for a short period. This ensures that the UI reflects the login status more accurately and promptly after the user completes the authentication flow in their browser. - **Error Handling:** Added more specific error messages for failed token exchanges and invalid SSO responses. **System Name Resolution:** - **Multi-stage Resolution:** The `ResolveSystemIDByName` function now employs a more robust, multi-stage approach to find system IDs: 1. It first attempts to use the `universe/ids` endpoint for direct name-to-ID mapping, which is generally more accurate. 2. If that fails, it falls back to a `strict` search via the `search` endpoint. 3. As a final fallback, it performs a non-strict search and then resolves the names of the returned IDs to find an exact case-insensitive match. If no exact match is found, it returns the first result. - **Logging:** Added more detailed logging for each stage of the system name resolution process, aiding in debugging. - **ESI API Headers:** Ensured that necessary headers like `Accept` and `X-User-Agent` are correctly set for ESI API requests. **Frontend Changes:** - **Import `ESILoggedIn`:** The `ESILoggedIn` function is now imported into the `Header.tsx` component. - **Updated Toast Message:** The toast message for setting a destination now includes the system name for better context in case of errors.
README
About
This is the official Wails Vanilla template.
You can configure the project by editing wails.json
. More information about the project settings can be found
here: https://wails.io/docs/reference/project-config
Live Development
To run in live development mode, run wails dev
in the project directory. This will run a Vite development
server that will provide very fast hot reload of your frontend changes. If you want to develop in a browser
and have access to your Go methods, there is also a dev server that runs on http://localhost:34115. Connect
to this in your browser, and you can call your Go code from devtools.
Building
To build a redistributable, production mode package, use wails build
.
Description
v4.1.0
Latest
Languages
TypeScript
86.9%
Go
8.8%
JavaScript
2.8%
CSS
0.8%
Shell
0.5%