Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support output path maps/alias #136

Closed
SkyaTura opened this issue Jul 24, 2022 · 1 comment
Closed

Support output path maps/alias #136

SkyaTura opened this issue Jul 24, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@SkyaTura
Copy link
Contributor

Path alias is already a useful feature when running code analysis, however, the output is always path relative to the found module.

This may not be always desirable, like, for instance, when working with modular projects and/or monorepos, since the output will be outside the scope of the main project.

I'm already trying some solutions for this one, but I need further testing to make sure it doesn't break anything.

Probably there will be more feature requests related to modular projects, but I'm hoping this one will be enough.

@samchon samchon added the enhancement New feature or request label Jul 25, 2022
@samchon
Copy link
Owner

samchon commented Aug 12, 2022

When defining nestia.config.ts file, I'll let developer to assign module instance.

Then this problem would be solved.

export interface IConfiguration {
    module?: object;
}

@samchon samchon closed this as completed Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants