-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug 466. Rules without a subscription cannot be listed. Listing rules for an invalid DID causes infinite loading #469
Conversation
const data = this.transformResponseModel(responseModel, dto) | ||
const status = data.status | ||
if (status === 'success') { | ||
return data as TResponseModel |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are the changes that allow the subscriptions to be optional. Basically, the transformResponseModel function is now responsible for determining whether the postprocessing pipeline element output is optional.
} | ||
} | ||
|
||
class OptionalResponsePipelineElement extends BaseStreamingPostProcessingPipelineElement< |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test had to be changed to feature different types of pipeline elements, as now they themselves determine error handling
TODO: determine if there are any pipeline usecases that need to discard errors |
Should the API tests be refactored? Like with utils and fixtures decomposed |
Critical/error to handle this |
7eb1203
to
db6ea02
Compare
@MytsV looks good to go! Could you refactor the pipeline element :) |
…ed behaviour Whether the error is passed on is decided by the implementation of the pipeline element
…over this by a test
…over this by a test
db6ea02
to
3534296
Compare
Fix #466
Cover this behavior with tests.