snorkel/root-repository-maintenance-4a9d6ef2d06f43
2
0
Fork 0
Code Issues Pull requests 5 Projects Releases Packages Wiki Activity

fix-fader-level-example: Correct fader level method in mixer connection README #1

Open
std-bot wants to merge 2 commits from task/fix-fader-level-example into main
pull from: task/fix-fader-level-example
merge into: snorkel:main
Conversation 0 Commits 2 Files changed 284 +59835 -181
std-bot commented 2026-06-07 17:39:49 +00:00
First-time contributor
Copy link

Assigned idea

The mixer connection README shows conn.master.setFaderLavel(0.5);, while the nearby feedback stream uses `faderLevel## Assigned idea

. Update the documentation example so the fader setter spelling is consistent and discoverable for users copying the initialization sample.

Approach: Inspect the public API for the master fader setter, then update packages/mixer-connection/README.md to use the correct method name in the example. If the misspelled method is also present in code, keep this change scoped to documentation unless a compatibility-safe alias is already part of the package conventions.

Verification: Run grep -n "setFaderLavel\|setFaderLevel" packages/mixer-connection/README.md to confirm the README uses the corrected spelling, then run the repository documentation or package checks available from the root package scripts, such as npm test or npm run lint if present.

Risk: Low risk because this is a documentation-focused correction. The main risk is choosing a method name that does not match the actual exported API, so the implementation should verify the source or type definitions before editing the README.

Agent context

Task slug: fix-fader-level-example
Branch: task/fix-fader-level-example

## Assigned idea The mixer connection README shows `conn.master.setFaderLavel(0.5);`, while the nearby feedback stream uses `faderLevel## Assigned idea . Update the documentation example so the fader setter spelling is consistent and discoverable for users copying the initialization sample. Approach: Inspect the public API for the master fader setter, then update `packages/mixer-connection/README.md` to use the correct method name in the example. If the misspelled method is also present in code, keep this change scoped to documentation unless a compatibility-safe alias is already part of the package conventions. Verification: Run `grep -n "setFaderLavel\|setFaderLevel" packages/mixer-connection/README.md` to confirm the README uses the corrected spelling, then run the repository documentation or package checks available from the root package scripts, such as `npm test` or `npm run lint` if present. Risk: Low risk because this is a documentation-focused correction. The main risk is choosing a method name that does not match the actual exported API, so the implementation should verify the source or type definitions before editing the README. ## Agent context Task slug: fix-fader-level-example Branch: task/fix-fader-level-example <!-- std-ts:idea-pr-body -->
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin task/fix-fader-level-example:task/fix-fader-level-example
git switch task/fix-fader-level-example

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff task/fix-fader-level-example
git switch task/fix-fader-level-example
git rebase main
git switch main
git merge --ff-only task/fix-fader-level-example
git switch task/fix-fader-level-example
git rebase main
git switch main
git merge --no-ff task/fix-fader-level-example
git switch main
git merge --squash task/fix-fader-level-example
git switch main
git merge --ff-only task/fix-fader-level-example
git switch main
git merge task/fix-fader-level-example
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
snorkel/root-repository-maintenance-4a9d6ef2d06f43!1
No description provided.