You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd love the ability to "leave out" chunks of the module-path.
For example, in a project named bs-slash-create, BuckleScript by default 'namespaces' the project's modules underneath a module of the same name, SlashCreate. In simple projects with only one root module, this can result in a doubled module-path, i.e. SlashCreate.SlashCreate.
When running bsdoc build SlashCreate in such a project, a directory-structure like this is produced:
Ideally, bsdoc would allow me to explicitly strip particular components, and then discard any modules that are inaccessible by the newly-stripped path (i.e. bsdoc build SlashCreate --strip SlashCreate.SlashCreate producing SlashCommand, User, etc at the top-level of the docs.)
Alternatively, at the least, it'd be nice if bsdoc respected the "namespace" field in bsconfig.json:
I'd love the ability to "leave out" chunks of the module-path.
For example, in a project named
bs-slash-create
, BuckleScript by default 'namespaces' the project's modules underneath a module of the same name,SlashCreate
. In simple projects with only one root module, this can result in a doubled module-path, i.e.SlashCreate.SlashCreate
.When running
bsdoc build SlashCreate
in such a project, a directory-structure like this is produced:When published to GitHub Pages, this results in URLs like:
Ideally,
bsdoc
would allow me to explicitly strip particular components, and then discard any modules that are inaccessible by the newly-stripped path (i.e.bsdoc build SlashCreate --strip SlashCreate.SlashCreate
producingSlashCommand
,User
, etc at the top-level of the docs.)Alternatively, at the least, it'd be nice if
bsdoc
respected the"namespace"
field inbsconfig.json
:... and didn't produce an additional top-level
SlashCreate
when that is thusly configured.The text was updated successfully, but these errors were encountered: