Problems when rendering globbing paths about fsharp.formatting HOT 11 CLOSED

Hmm... I'm not entirely sure what to do here, because *whatever* is Markdown command for italics - this does not make too much sense for your sample, but I'm not sure how we could determine that.

Perhaps you could format paths in the documentation as inline code using backticks. Something like:

which are specified in `"./**/packages.config"` 

I believe that should work and it should be turned into:

which are specified in "./**/packages.config"

from fsharp.formatting.

Actually I can change it to normal style if it's to difficult.

from fsharp.formatting.

It's tricky, because

• *foo**bar* should become [em]foo**bar[/em] but
• *foo**bar**goo* should become [em]foo[strong]bar[/strong]goo[/em] (I guess, although SO doesn't do this)
• but I have no idea what would be the expected result for e.g. *foo**b*r**goo*

...but I guess it's doable. When looking for the end of an inline formatting command, we could continue searching until we find something with a well-balanced body (now, we just look for the first possible ending point). The specification is not particularly clear.

Also, I think you should be able to escape things using \ so try *"./\*\*/packages.config"* (if that does not work, then that's a bug). This does not seem to work on GitHub

_"./_/packages.config"

but it does work on StackOverflow...

from fsharp.formatting.

I tried to escape - didn't work

from fsharp.formatting.

Thanks, I'll look into that!

from fsharp.formatting.

Escaping should now work. Let me know if it does not.

from fsharp.formatting.

yay. works.

Are there any other changes in the last release? Do I need to update my templates?

from fsharp.formatting.

I just pushed a new version to NuGet, which does not bring anything significantly new, but changes how the templating is handled (so you can have just a single template for documentation generated from scripts and API reference).

Also, the templates are included in the NuGet package, so you can only edit the master template (with links etc.) but just use module/type/namespace templates from the package - so hopefully you won't need to update those yourself.

See the details (and sample usage) here: fsprojects/ProjectScaffold#12

from fsharp.formatting.

This? fsprojects/FAKE@5d6b6cf

from fsharp.formatting.

This is part of it - it lets you specify multiple template paths, so that you can include both the standard ones (in the FSharp.Formatting NuGet package) and a path with your own customized templates (your should be first, to override the default ones).

from fsharp.formatting.

Mhm. all I want to do at the moment is to customize the menu.

The other stuff can be used from the default templates

from fsharp.formatting.