Open francotiveron opened 6 years ago
@francotiveron These are limtations with the type provider support in F# tooling. I need to dig in to it a bit more, but I've adjusted your report to now clarify that the recommendation is to avoid authoriung type providers with a single optional static parameter.
Description
Two known limitation exists when a type provider has a single optional parameter.
The optional parameter can not be omitted completely
The optional parameter can not have an actual value that is identical to the default value
As a result, type provider authors should avoid type providers with a single optional parameter
Description (original)
I have a very basic type provider with one static parameter:
And a using code in a different project
Repro steps
I find two different issues
1. Static parameter = "" (empty string)
2. Static parameter unspecified
Having specified the default value for the static parameter, I expect I can call the type provider without it. To corroborate this expectancy, the intellisense tooltip (Visual Studio 2017) coming up on the < character shows
Nevertheless, the declaration is not accepted, as follows