Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Server nil returns cause problems #532

@ashishgandhi

Description

@ashishgandhi

In Go it is pretty idiomatic to return nil, err from a func when we encounter an error when the return values are a pointer and an error. The servers fail to marshal this nil while sending back a response to the client; and fatal logs. I think it might be better to do new(T) for the user before marshaling.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions