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

MonoRepo Support #927

Open
whatthehanan opened this issue Jun 28, 2022 · 1 comment
Open

MonoRepo Support #927

whatthehanan opened this issue Jun 28, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@whatthehanan
Copy link

I'm submitting a...


[ ] Regression 
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

if in a nestjs monorepo I run the nest add @nestjs/azure-func-http it asks for destination project and creates a azure function for it but if you run in twice it overrides the existing azure function to use the new project

Expected behavior

running nest add @nestjs/azure-func-http and selecting different projects should create multiple azure functions

Minimal reproduction of the problem with instructions

nest new demo
cd demo
nest generate app models
nest add @nestjs/azure-func-http (select demo project)
nest add @nestjs/azure-func-http (select models project)

What is the motivation / use case for changing the behavior?

I'd like to use one repo for multiple azure functions

Environment


Nest version: 8.2.8

 
For Tooling issues:
- Node version: 16  
- Platform: Mac 

Others:

@kamilmysliwiec
Copy link
Member

Would you like to create a PR for this feature?

@kamilmysliwiec kamilmysliwiec added the enhancement New feature or request label Feb 9, 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