react-leaflet-canvas-overl VS null

1. React Leaflet canvas overlay. Leaflet is a popular mapping library and React Leaflet brings the declarative nature of React to the Leaflet api. I needed to display some 3D rendered shadows on a map and needed to overlay a canvas at specific lat/lng bounds so I made a React component to plug into React Leaflet.

2. I needed a solution for recording Twilio live video and hosting it myself in S3. I made a docker container that launches Chrome headless, points it at any website (including a Twilio video conference) and uses and Chrome extension to record the screen and stream it to S3. In theory it could be used to record any website on the internet.

[1] https://github.com/ted-piotrowski/react-leaflet-canvas-overl...

Use-case: working on PATCH requests, the body may or may not contain nullable values. I am using guregu/null and I can't use a pointer because if the json contains "null" as a value, the pointer will be set to nil in the struct, instead of a value representing the presence of null. In short I can't differentiate the absence of the field in the request from the presence of the field with a null value.

https://github.com/guregu/null is an awesome package implementing most SQL scanner Interfaces plus JSON

There’s also this: https://github.com/guregu/null

Unfortunately in Go, switching to *bool makes the api a little more awkward to use since users that need to set true or false have to define a local variable then use a pointer to that. Another option would be something like null, but that adds a dependency to your currently-dependency-free project. If anyone has a better solution to this pattern, I'd love to hear it.