Add Transformer class for live HTTP objects #328
Merged
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.
To make Styx APIs safer for the end-users, this PR adds a separate
Transformer
alongsideBuilder
inLiveHttpRequest
andLiveHttpResponse
classes. The transformer restricts what the API consumers can do 1) when creating a new live HTTP object and 2) when transforming one.Some examples:
It is no longer possible to replace, and thus disconnect the reactive
ByteStream
chain like so:The transformer class now enforces API consumers to transform the byte stream with the lambda alternative. Like so:
Likewise it is no longer possible to supply a mapper lambda when creating a live object. This is no longer possible: