Maxime Mangel

Not only the binding needs to be updated to support nullness supports but we will also need to update the FCS fork that Fable use so we can get access...

I am tracking the nullness supports in Glutinum project [here](https://github.com/glutinum-org/cli/issues/121). It ask questions regarding how things should be represented. It could also be a good time for checking how Glutinum...

> Consumers of Fable bindings also need to enable nullness checking in their projects, meaning we don't need to publish a separate set of packages with nullness metadata - it's...

Ah yes right, this is one of the reason we use F# after all 😅 (sometimes you forget some of the simplest things).

If we need to duplicate the API surface to support nullness then I will probably vote against it, we need to either commit to it or keep using Option for...

I decided to move this issue into Fable repository because there is more to decide that the aesthetic of the API. @ncave As you probably know more about FCS +...

> but then we'll also need to add `net9.0` TFMs so that nullness warnings show up in the IDE, and users also need to retarget their Fable projects to `net9.0`...

> > Duplicating the API surface means depending on your configuration you have a different API > > Technically speaking, I'd say it's the same API surface with extra metadata....

Thanks both of you for your input. Personally, my current position is: 1. We add support for `nullness` in Fable, because we want feature parity regarding F# specs/language. I think...

I am starting to look at how to implement `Nullable` in Fable. I think we could map `Nullable` to check against only `null` in JavaScript. My idea being, once F#...