mapbox-gl-js VS io-ts

Good. Brave's fiddling with WebGL causes >50% of my bug reports from 1% of users.

[1] https://github.com/mapbox/mapbox-gl-js/issues/10518

[2] https://github.com/mapbox/mapbox-gl-js/issues/8377

Laravel and Mapbox GL JS

It originated as an open-source fork of Mapbox-gl-js before they switched to a non-open-source license on 8th December 2020.

Do you have programming skills? MapboxGL JS is a great library for stuff like this, you can really easily add a layer of GeoJSON data to a map. If you're looking for something less technical Google map lets you create custom maps where you can add a bunch of pins.

From the latest commits (not released/stable yet): git clone https://github.com/mapbox/mapbox-gl-js.git yarn install yarn run build-prod-min yarn run build-css Then use the generated mapbox-gl.js and mapbox-gl.css files. See CONTRIBUTING.md for more details.

> too bad it doesn't come with some code

Mapbox changed the license of their code last year I think to a proprietary one. https://github.com/mapbox/mapbox-gl-js/blob/main/LICENSE.txt

It requires a mapbox user license with billing enabled to use this code, let alone make modifications. But the source is viewable on github.

The software stopped being open source from v2 onwards. The new licence makes it merely shared source.

This GitHub issue where this change is announced provides a number of more in-depth explanations why this is a bad thing for most users of the software: https://github.com/mapbox/mapbox-gl-js/issues/10162

It's a bummer mapbox isn't open source anymore, now you're (and lots of other peoplare) are stuck pre-2.0.0 :(

https://github.com/mapbox/mapbox-gl-js/blob/main/CHANGELOG.m...

Qué rico. Si tenés chance meté un proceso de code review fuerte, y para el tema de I/O probá a usar https://github.com/Effect-TS/schema ó https://github.com/gcanti/io-ts que les da una solución obvia al tema de "tipos para lo que devuelva el backend", aunque es en realidad mucho más capaz que eso.

My fave is still io-ts (https://github.com/gcanti/io-ts/blob/master/docs/index.md) as I find it more flexible than zod at the ingress. The author is also working on the Effect ecosystem which also looks interesting.

I’ve been using io-ts for this and been very happy with it. [1] It’s similar to Swift’s Coding protocol in case you’re familiar.

[1] https://gcanti.github.io/io-ts/

Yeah, there are a few new concepts and it's not the easiest to pick up right away. The best introduction is here on the main documentation page.

We use https://github.com/gcanti/io-ts/blob/master/Decoder.md which has a very similar interface. It can even be used to mutate the data using https://github.com/gcanti/io-ts/blob/master/Decoder.md#the-parse-combinator.

A good way to significantly improve the reliability of your app is via improving type-safety by moving away from using any to unknown. One relevant example could be when you type your backend responses and when stringifying JSON to using unknown combined with some sort of runtime type checking. It can be done either by using built-in functionality like type guards or using an external library like io-ts, zod or yup.

Usage of TypeBox is similar with io-ts and zod, but it is much powerful and faster than them. Also, TypeBox can generate JSON schema very easily. Therefore, if you're looking for a validator library for new project and not suffering from legacy codes, I think TypeBox would be much better choice than io-ts and zod. TypeBox can totally replace them.

This check can be done with different libraries like: io-ts, typebox, or zod. These libraries allow you to create objects that represent your typescript definitions. Then, these objects can be used at runtime to validate the received data, in addition, you can also convert this object to a Typescript definition to have all the benefits of using typescript. These objects can be called schema validations because they are responsible for the data validation.