Added support of unmarshalling and marshalling of pointers #32
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.
During development of my own project I found some issues when trying to marshal php Nulls
N
into any Go struct fields.Was seeing uncaught panics such as
reflect: call of reflect.Value.Set on zero Value
if the value trying to be set on a struct field was Null.Additionally if a value was being set on a struct field of type reflect.Ptr that was nil a panic would occur when calling the .Set method on the struct field e.g.
reflect.Set: value of type string is not assignable to type *string
I've added testing to showcase the now supported functionality:
I used this Go playground to try base behaviour off of the
encoding/json
package: https://go.dev/play/p/5td0XqinlIP