I prefer that configuration files all have a dot prefix''and ESDoc hosting is looking for esdoc.json
Could you add an exception for .esdoc.json as well? Or better, add a field that lets the user say what their configuration file is called during the hosting generation step?
I prefer that configuration files all have a dot prefix''and ESDoc hosting is looking for esdoc.json
Could you add an exception for
.esdoc.json
as well? Or better, add a field that lets the user say what their configuration file is called during the hosting generation step?