Skip to content

Correct which settings apply without hyper.settings.client - #19

Open
jlnstrk wants to merge 1 commit into
mainfrom
jlnstrk/settings-fallback-doc
Open

jlnstrk wants to merge 1 commit into
mainfrom
jlnstrk/settings-fallback-doc

Conversation

@jlnstrk

@jlnstrk jlnstrk commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Today, the doc on apply_all_settings says that on a hyper.video deployment without hyper.settings.client, the transport and the microphone and camera state still apply. Since #16, the transport is a hyper.settings.client edit too, so there its step fails like the other six settings steps. Only the microphone, camera and screen share steps apply, because they click the web app's buttons. The participant connects with the deployment's default transport. A run against pr-6082.dev.hyper.video showed this: seven Failed to apply … lines, and --transport webrtc connected over WebTransport.

This corrects the doc and changes no code.

Please merge this before tagging v0.7.0 (#18), so that the release carries the corrected doc.

The transport is a `hyper.settings.client` edit too, so on a deployment
of hyper.video without it, the transport step fails like the other
settings steps. Only the microphone, camera and screen share steps
apply, and the participant connects with that deployment's default
transport.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant