Repository navigation
Conversation
Member
|
hey, sorry for the delay, giving me two options froze me lol. will discuss with the team this week, we also want to expose openapi docs on the website as well. |
Author
|
No problem! Yeah sorry if it was overwhelming haha |
1 similar comment
Author
|
No problem! Yeah sorry if it was overwhelming haha |
github-actions
Bot
force-pushed
the
dev
branch
from
September 29, 2025 05:53
f16de3d to
cc0d460
Compare
github-actions
Bot
force-pushed
the
dev
branch
from
November 10, 2025 05:43
772b621 to
eb855e1
Compare
github-actions
Bot
force-pushed
the
dev
branch
3 times, most recently
from
November 22, 2025 18:07
f1dc981 to
3e15a39
Compare
github-actions
Bot
force-pushed
the
dev
branch
3 times, most recently
from
November 27, 2025 01:29
f8ee907 to
6a9856d
Compare
bussard76
pushed a commit
to bussard76/openwork
that referenced
this pull request
May 12, 2026
* fix: prevent session loss when switching workspaces Add guard to prevent clearing sidebar sessions when the session store temporarily returns empty during worker restart/reconnect. This fixes the issue where sessions disappear from the sidebar when switching between workspaces or refreshing the window. Fixes anomalyco#750, anomalyco#735 * feat(app): add shouldUpdateSidebarSessions pure function with tests Extract the guard logic from app.tsx into a testable pure function to prevent session loss during workspace switches. - Add `shouldUpdateSidebarSessions` to `lib/sidebar-sessions-guard.ts` - Add test script `scripts/sidebar-sessions-guard.mjs` with 7 test cases - Update app.tsx to use the extracted function - Add `test:sidebar-sessions-guard` script to package.json The guard prevents the sidebar from being cleared when the server temporarily returns an empty session list during worker restart/reconnect. Ref: anomalyco#750
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds Swagger UI support to the opencode server, providing an interactive API documentation interface.
Changes
@hono/swagger-uidependency/uiendpoint/docImplementation
I followed the standard Hono Swagger UI documentation approach as shown in their official examples. This provides a clean, minimal integration that leverages our existing OpenAPI specification.
Proposal: support both Swagger UI and Scalar UI
See also #791 which implements Scalar UI on
/scalaras an alternative documentation interface. Both UIs can coexist without conflict.I believe we could support both documentation UIs simultaneously:
/ui- The industry standard that most developers are familiar with/scalar- A modern alternative with enhanced featuresThis would give users choice based on their preferences and use cases.
What do you think? Should we support both, or would you prefer to choose one? I'm open to discussion!