Repository navigation
Conversation
Expose the Label service over /api/label (list, get, create, update, remove). Label schemas move to @opencode-ai/schema so Protocol can reference them without depending on Core. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3 of 6 tasks
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.
Issue for this PR
Closes #17
Type of change
What does this PR do?
Built on top of #20, this PR creates 5 API endpoints to reach the Label Service: GET /api/label (list), GET /api/label/:labelID (get), POST /api/label (create), PATCH /api/label/:labelID (rename or move) and DELETE /api/label/:labelID (remove). Appropriate label logic is implemented, such as deleting a parent label deletes all nested labels. The endpoints are defined in packages/protocol and handled in packages/server. Valid HTTP responses are returned for different requests.
How did you verify your code works?
Started a temporary server at a throaway database (OPENCODE_DB=/tmp/labels-demo.db bun dev serve --port 4096) and tested curl commands against it, verifying correct http responses for different requests.
Screenshots / recordings
N/A
Checklist
If you do not follow this template your PR will be automatically rejected.