Support for generating docs for type providers #143
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I also didn't have type to add tests for this, but it generate this successfully: |
tpetricek
added a commit
that referenced
this pull request
Mar 10, 2014
Support for generating docs for type providers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a very hacky solution, as FCS doesn't support this. The xml docs of type providers don't even go to the generated xml doc from the compiler, you only get a bunch of
<member name=""></member>.What this does is look at the xml docs and get the names of the static params, but it's not able to get neither the type, default value or optionality. And if the xmldocs don't document all the parameters, they won't go into the fsharp.formatting generated docs