test: added a lot tests around the monorepo structure

[Jefiozie]

Hi @kamilmysliwiec,

Here is my draft PR with an explanation of what I've changed and what the behavior is/ will be. I will split this in two different part, part one is for the default setup that is not a monorepo. The other one is specific for the monorepo setup.

Default setup

To use the library people do the following:

1. nest new projectName
2. nest add @nestjs/azure-func-http
3. npm run start:azure

The output of this will be the same as earlier. In the dist folder will be all the code and because of the configuration in the Azure files it will be runnable by running func host start

No new things there, the only thing I would like to know. Should we support a nest.json file? This is something I've not yet implemented at this moment.

Monorepo setup

To use the library people do the following:

1. nest new projectName
2. nest generate app projectTwo
3. Under the hood it will be transformed to a monorepo workspace
4. nest add @nestjs/azure-func-http --project projectTwo
5. nest build projectTwo
6. Under the hood, we will publish in the dist/apps/projectTwo with a custom webpack setup
7. cd apps/projectTwo/src
8. npx func host start

The output of the dist will be runnable similiar as the Default Setup

Could you provide me some feedback and the answer if we need to support nest.json. I don't know if the custom webpack setup is the best way to go as this will break the default behavior of nest start projectTwo. But I don't see a other way we could do this.

I hope this is approach you like to go with this package. It is pretty hard to configure all of the different parts.
]

[Jefiozie]

Also, I can't figure out why the test fail and the order of files is different there from local.

[Jefiozie]

I'm also available to chat about it if you would like that

[Jefiozie]

Hi @kamilmysliwiec just checking in to see if this approach is what we want to implement? 😁

[kamilmysliwiec]

Will review tomorrow! Apologies on the delay

[kamilmysliwiec]

Could you provide me some feedback and the answer if we need to support nest.json. I don't know if the custom webpack setup is the best way to go as this will break the default behavior of nest start projectTwo. But I don't see a other way we could do this.

I think we can add the custom webpack setup :) Not a big deal

[Jefiozie]

@kamilmysliwiec I made the change as requested. What do you think about the extra flag if added --project to determine the project it should be added. Is this a valid approach our should we get it via --sourceRoot

[kamilmysliwiec]

--project sounds a bit more descriptive (IMO)

[kamilmysliwiec]

@Jefiozie I can see that you marked this PR as ready for review, but the title states "still wip". 😅 Do you think I can give it a shot already?

[Jefiozie]

@kamilmysliwiec oops, I changed it straight away. I think with these changes we have all the scenarios covered. However maybe I'm missing something I tried to make and create as much tests as possible.

[kamilmysliwiec]

OK thanks! i'll review asap

[kamilmysliwiec]

Looks amazing!