Erlend Hamnaberg
Erlend Hamnaberg
this is apparently using pure javascript JSON.parse, then converting after, so I guess standard javascript semantics should be expected.
would you mind fixing the merge conflicts here and we'll get a real review started.
I'm not sure we want two concepts for representing Json.Nullable things. `Option` is fine for that. We might want something that represents the possible missing value as a type, So...
> I wouldn't mind having this approach, if it can be done. > > Btw, there's `UndefOr` in scala-js, exactly for this purpose, so it would be nice to have...
We should keep the old behavior as default until next major release.
I am not happy with the NullOr name, but I dont really have a better suggestion. https://www.merriam-webster.com/thesaurus/undefined does not really help either. `MurkyOr` does not really inspire confidence.
Does this still happen?
Moving refined here: #2276
I did not see this before now. I apologize. Has this been resolved, or did you pay for another year?