wneessen/niljson
1
0
Fork 0
mirror of https://github.com/wneessen/niljson.git synced 2024-10-06 01:35:57 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fix typo and improve readability in README.md

Browse source 
Corrected misspelling of 'niljson' and clarified punctuation. These changes enhance the clarity of sentences, ensuring better readability and comprehension for users.
This commit is contained in:
Winni Neessen 2024-09-11 11:08:03 +02:00
parent 7bddca99ae
commit bc611894a8
Signed by: wneessen
GPG key ID: 385AC9889632126E
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -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.