Example tests for Solid Notifications and WebSocketSubscription2021 specifications #86
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.
This is some provisional work on testing these notifications related specs. Of note:
@notifications
tag.protocol
don't specify a subscription type as they are meant to test the protocol, not a particular subscription type. Since the discovery mechanism is not yet specifiedsubscription-endpoint.feature
uses an alternative implementation and defaults toWebSocketSubscription2021
. It also contains code which should allow it to pick the first available subscription type after notification channel discovery but this is untested as there are no implementations available.solid-0.1
protocol since that is insecure and will not be retained in the Solid specification.Comments on this would be very welcome.