Convert component guidelines to markdown (attempt #1) #374
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
fsgit
added a commit
that referenced
this pull request
Dec 11, 2014
Convert component guidelines to markdown (attempt #1)
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 converts the component design guidelines to markdown so we can better evolve this document as a community.
It's an open question as to whether these guidelines should be under http://fsharp.org/specs or elsewhere (e.g. http://fsharp.github.io). I'm leaving them here for now, with converted format.
The markdown will undoubtedly need some tweaking, e.g. because of the use of unicode characters etc.