Oskar Gewalli

Should be. It would be nice to have it verified for both the 1 and 2 versions.

One way to do it would be to inspect compiled usage in order to verify that the correct overload has been chosen by the compiler.

https://hackage.haskell.org/package/base-4.12.0.0/docs/Control-Applicative.html#v:-60--42--42--62- Same as but with arguments flipped

Yes, my feeling as well. Though question is how common the case of deep map is?

Perhaps a module function in order to hold off on defining a new operator?

Looks like an FsDocs issue. Perhaps forgotten to markdown escape function names?

Perhaps another thing we can do is have a remark in the doc text about the issue in order to make it less weird on the site.

Could be https://github.com/fsprojects/FSharp.Formatting/pull/765/ I'll try to upgrade F# formatting and see if it fixes things

Any thoughts on where to put the documentation? I've added some PRs related to minimal API code on the samples repository.

I agree that the example you show is better. Perhaps the reason why you have MapGet as a thing directly is because that is a route declaration.