Skip to content

MonoRepo Support #927

@whatthehanan

Description

@whatthehanan

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:

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions