Generated paths do not work when generated content is pushed to Git.

[steeren]

Love the generator, has a lot of promise, but...

I'm generating our api with the intent of using it as browsable content on our Git server (in our case GitLab). I have pointed to a templatesDir and that appears to work for customizing the appearance of a class, but for the life of me I cannot effect what is rendered in the contentsFile.
For the contentsFile, the generated paths are all wrong. Because I build this on a windows machine, it uses backslashes in the paths, which means it all fails when I upload it to GitLab. Users can see the contentsFile but all links within it, use backslashes not forward slashes so none of the links are valid.
I used string-replace to get round this but the paths start with a slash (/) and in order to get it to work correctly so all paths are relative to the contentFile, I need it to start with dot-slash (./).

Essentially, there needs to be a means of formatting the path so developers not fortunate enough to be allowed use anything other than windows in their company, have a chance at using this.