Nensec

We seem to appear to have the same problem here, "x-nullable" is always true Edit: This is not entirely correct, the only time parameters are always nullable is if they...

[NotNull] appears to work. Though it feels counter intuitive having to mark parameters as required when they have no default value just because they can be null, compared to explicitly...

Perhaps this could be integrated somehow in the Shift-M mini-mapview?