Custom module name formatter does not work for 'nested' namespaces

Issue #84 closed
Cosmin Lazar
created an issue

The current custom module name functionality is implemented by taking note of the original namespace and the custom module name, then once the typescript string has been generated the original namespaces are string replaced with the new ones. Of course this causes issues when one namespace is a substring of another.

Will soon submit a pull request that deals with the error.

Comments (2)

  1. Log in to comment