This repository has been archived by the owner on Mar 1, 2024. It is now read-only.
Exposed websocketController and webXRController to public API #124
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In
library/the public API is a bit too locked down currently and prevents some common customizations, for example:Users are unable to send or respond to custom websocket message without
websocketControllerexposed.Similarly, users are unable to configure their VR experience programmatically without the
webXrControllerexposed.These two controller have been exposed in this PR.
In
ui-library/theSettingsUI*types are not exposed, these allow the users to add custom settings.These types have been exposed in this PR.