feat(controls-plugin): compose sections across hook instances#292
Open
draggie wants to merge 4 commits into
Open
feat(controls-plugin): compose sections across hook instances#292draggie wants to merge 4 commits into
draggie wants to merge 4 commits into
Conversation
… plugins (callstackincubator#291) ## Description Adds two community Rozenite plugins to the plugin directory: - **rozenite-zustand-devtools**: DevTools plugin for inspecting Zustand store state in React Native apps (https://github.com/IronTony/rozenite-zustand-devtools) - **rozenite-navigation-inspector**: DevTools plugin for inspecting navigation state in Expo Router / React Navigation apps (https://github.com/IronTony/rozenite-navigation-inspector) Both entries were appended to `plugin-directory.json` with the standard `npmUrl` + `githubUrl` fields. Both packages are published on npm and both repositories are public. ## Related Issue N/A, this follows the documented "open a pull request to contribute your plugin to this list" flow on the plugin directory page. Happy to open a tracking issue first if maintainers prefer. ## Context `plugin-directory.json` is the source of truth for the directory; all other metadata (version, description, star count, official badge) is resolved at build time from the npm registry and GitHub API, so no extra fields are needed. Both plugins are community-scoped (not `@rozenite/`), so they render with `isOfficial=false`, consistent with existing community entries like `rozenite-growthbook-plugin` and `zorro`. GitHub URLs point to the repo roots, matching the convention for standalone community repos. ## Testing - Validated `plugin-directory.json` parses cleanly (`node -e "JSON.parse(...)"`), no trailing-comma or syntax errors. - Confirmed both npm package URLs resolve (rozenite-zustand-devtools v1.0.2, rozenite-navigation-inspector v1.1.1) and both GitHub repos are public. - Verified the diff touches only `plugin-directory.json` (8 lines added).
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
2 participants
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.
Description
Adds support for composing Controls Plugin sections from multiple
useRozeniteControlsPluginhook instances. The hook now accepts either options or an updater function, so components can
extend previously registered sections instead of replacing them.
Related Issue
Fixes #284
Context
Previously, each hook instance sent its own full snapshot, so the last mounted/updated
component could overwrite controls registered elsewhere. This change adds a shared registry
that combines active registrations and keeps UI, updates, actions, and agent tools resolved
against the composed section list.
Testing
Extra Section; confirmedboth original controls and extra section appear and the extra toggle works.