Future directions about fsharp.formatting HOT 2 CLOSED

Thanks for starting this discussion and sorry for not getting back earlier. I think the best way to manage the TODO list is to post issues here on GitHub and then we can prioritize and coordinate. I would very much welcome contributors (and I'll try to be a bit more active in managing the project...)

The main two big things that I would like to get done are:

• Finish the replacement for FsHtmlDoc
• Turn the literate.fsx script into a project - the file is getting too long and messy. I think there should be some discriminated union representing literate script (with two functions that load this - from fsx file and from md file). You should then be able to pre-process the document before generating HTML/latex. I think this is mainly refactoring work...
• Unit tests - we should have some :-) there is a project that compares our Markdown translator to a one in C#, so turning that into NUnit test would be great. I think tests for the literate.fsx script could be more easily done after the refactoring I mentioned.

These are the things I need for my projects at the moment, but I think there are other important extensions - if you're interested in improving the math support, that would be fantastic!

from fsharp.formatting.

I made some reorganizations in the project structure, so it should be easier to make progress now.

• I'm including working prototype of FsHtmlDoc (in the new NuGet package)
• literate.fsx is now an ordinary project, so it should be easy to work on it (it badly needs some restructuring)
• I created some unit tests for CodeFormat, but we need more ... but they can now be easily added

from fsharp.formatting.