mirror of
https://github.com/wneessen/niljson.git
synced 2024-11-25 15:00:49 +01:00
Merge pull request #9 from wneessen/update-readme
Fix typo and improve readability in README.md
This commit is contained in:
commit
ab766b23fa
1 changed files with 4 additions and 3 deletions
|
@ -14,10 +14,11 @@ SPDX-License-Identifier: CC0-1.0
|
||||||
|
|
||||||
niljson provides a simple and efficient way to handle nullable JSON fields during the (un-)marshalling process.
|
niljson provides a simple and efficient way to handle nullable JSON fields during the (un-)marshalling process.
|
||||||
In JSON, it's common to encounter fields that can be `null`, but handling these fields in Go can be cumbersome,
|
In JSON, it's common to encounter fields that can be `null`, but handling these fields in Go can be cumbersome,
|
||||||
especially when dealing with primitive types like `int`, `float64`, `bool`. These types can all be either `0` (as value)
|
especially when dealing with primitive types like `int`, `float64`, and `bool`. These types can all be either `0`
|
||||||
or `null`. In Go you can always work with pointers but these, of course, can lead to unhandled nil pointer dereferences.
|
(as a value) or `null`. In Go you can always work with pointers, but these can lead to unhandled nil
|
||||||
|
pointer dereferences.
|
||||||
|
|
||||||
**niljaon** addresses this challenge by offering a set of types that can seamlessly handle `null` values during
|
**niljson** addresses this challenge by offering a set of types that can seamlessly handle `null` values during
|
||||||
unmarshalling, allowing your Go applications to work with JSON data more naturally and with fewer boilerplate
|
unmarshalling, allowing your Go applications to work with JSON data more naturally and with fewer boilerplate
|
||||||
checks for `nil` values.
|
checks for `nil` values.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue