Handle instances where scope is returned as array in log entries #194
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.
🔧 Changes
This implements a custom
UnmarshalJSON
function for theLog
type that will handle the differing types ofscope
. Although this is documented to be astring
it appears in some instances (from checking, onlyfsa
type events) to be an array of strings.Unlike other instances where we have to implement this functionality, we do not need to implement a
MarshalJSON
function as we can only read theLog
type, i.e. there is no create or update functionality exposed.📚 References
#189
🔬 Testing
Covered by unit tests
📝 Checklist