Add per-space session abilities for manifest capability requests#58
Merged
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
1 participant
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.
Adds support for requesting distinct abilities per TinyCloud space during session creation.
This introduces
spaceAbilitiesonSessionConfig, allowing SDK callers to build one SIWE/ReCap request that spansmultiple spaces with different capability sets. The existing
abilitiesandadditionalSpacesbehavior remainsunchanged.
This is needed for manifest v1 composition, where app permissions may target the
applicationsspace while implicitregistry permissions target the
accountspace.Tested:
cargo test -p tinycloud-sdk-wasm parse_recap_with_distinct_space_abilitiescargo test -p tinycloud-sdk-wasm