[Query] Is it possible to import macros from angular library? about ng-doc

[akhileshThapliyal]

relative to your shared folder, then you'll need to use such paths for everything else, I could make an option for the builder to configure root path for file resolver if it will help you

Hi @skoropadas, np. I managed it. So I created an angular workspace where I have all the libs and projects co-exist. I am referencing using a relative path to the common macro file in one of the libs. Not sure whether this is optimal approach, but it helps me to keep the code clean, tidy and organised.

[skoropadas]

Yeah, it seems that nunjucks does not support the feature you're looking for. To implement the documentation in this way, I would recommend using an NX monorepo with multiple apps dedicated to documentation. This approach will allow you to have access to the source code and easily share some things between different documentation apps.

I also think that this is a good practice as it enables you to release the documentation and new library versions together. Additionally, it allows you to identify any errors that may arise during the compilation of the documentation app.

[akhileshThapliyal]

NX monorepo

NX monorepo is similar to Angular workspace. The problem with this is still the same, I need to refer the macros with hardcoded paths like ../../../../ and I cannot configure paths based on a configuration the way we define paths in the compiler option in tsconfig.app :(

[skoropadas]

NX monorepo

NX monorepo is similar to Angular workspace. The problem with this is still the same, I need to refer the macros with hardcoded paths like ../../../../ and I cannot configure paths based on a configuration the way we define paths in the compiler option in tsconfig.app :(

Well there is no workaround for that, because nunjucks uses one file resolver for everything, so if you e.g. start having paths relative to your shared folder, then you'll need to use such paths for everything else, I could make an option for the builder to configure root path for file resolver if it will help you

[maximLyakhov]

@skoropadas I have ng project with one library only meant to be published as package.
Currently it's described with storybook.
Tried to install ng-doc, but it partially failed due to absence of app.module.
Will ng-doc project support just libraries in foreseeable future?