-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: initial work on codegate version check widget #94
Conversation
Pull Request Test Coverage Report for Build 12828464111Details
💛 - Coveralls |
const resp = await fetch( | ||
new URL("/health", import.meta.env.VITE_BASE_API_URL), | ||
); | ||
const data = (await resp.json()) as unknown as HealthResponse; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this api is not integrated into the openapi in codegate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The health one isn't AFAIK — but the version one should be, that's a good point — once the BE work is in, we can generate it & use the API client.
I also noticed a bug in the previous PR where the client wouldn't be initialised with a base URL on first mount and we would make a request to a relative path of the frontend application — should investigate why that is as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's some discussion happening on best way to handle OpenAPI spec in discord — will come back and clean this up once that's settled.
Adds a second check to the "CodeGate Status" widget — depends on stacklok/codegate#612
Related to stacklok/codegate#555
Screen.Recording.2025-01-16.at.1.30.54.PM.mov