[Fix] Better handling of projection Faulted status #28
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.
Based on some real world results, just checking for
Faulted
is not good enough then because the UI will show a projection asFaulted (enabled)
which is actually some combination of strings.The eventstore docs do allude to this but it does not appear to show all possible states
https://developers.eventstore.com/clients/grpc/projections.html#projection-details
This change will check if the
Status
field contains theFaulted
sub-string. This prevents us getting in to a state where a projection is neitherStarted
,Stopped
, orFaulted
. That is still possible, but missing aFaulted
stated is critical and missingInitial
is not.