Fix parsing non-protected branches + simplify deserialization #89
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.
In #82 we
added a custom deserializer for the
Branch
class.This deserializer didn't handle certain cases properly that the GH API
would return. In particular the case where the
protected
field was setand no
protection_url
is present would lead to a NPE in thedeserializer.
To avoid this error and make the whole parser more resilient to
different API results, let's reduce the scope of the custom deserializer
to only parse the
protection_url
field instead of the wholeBranch
class.
There should be no change in runtime behavior apart from fixing the
error cases.