feat: read/write API for panels and tab trees - #2431
Open
valkenrath wants to merge 1 commit into
Open
Conversation
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.
Why
Firefox's tabs API does not expose Sidebery's panels, groups, or tree structure. Other extensions therefore cannot understand or safely modify the organization users maintain in Sidebery without depending on private storage.
This addresses the integration use cases discussed in #616.
Scope
This adds a typed extension-to-extension API. Exposes panel and tab-hierarchy state, supports moving branches, managing groups, and flattening hierarchy through Sidebery's existing services.
The change includes request validation, structured errors, documentation, and tests.
Firefox accepts messages from any installed extension by default, so this creates a general integration surface rather than an allowlisted one. Open to suggestion here.
Validation
npm run lint.typesnpm test -- --runnpm run buildweb-ext lint --source-dir addon