Introduction In part 1 we took a higher level view on serialization in general and JSON in specific. In part 2 we looked at emitting JSON. In part 3, we’ll look at an issue you might encounter when consuming JSON, Zero vs NULL field values. To clarify the definition of NULL, this means the absence of value. So here is the question: Given a field in a Go struct set to its zero value, how do you know that zero value was set by the user or it’s zero because it was never provided?

ArdLBS offers insights into location-based services (LBS) and geographic information systems (GIS), providing tutorials, case studies, and best practices for integrating location-aware features into applications. By exploring ArdLBS's curated content, developers can learn about geocoding, geofencing, routing algorithms, and spatial data visualization techniques for building location-based applications. Whether you're developing mobile apps, web platforms, or IoT solutions, ArdLBS offers resources to leverage location data and enhance user experiences.

Ardan Labs

Explores the challenge of distinguishing zero from null values in JSON while using Go. It presents three techniques to address this issue: pointer semantics, using maps, and applying default values, each with its advantages and drawbacks. The article provides code examples to illustrate each method and emphasizes the importance of appropriate JSON field validation.

The Fine Print: Part 3