Jackie McDoniel
Jackie McDoniel
I'll see how soon I can work on this
By the way @micalevisk if you want to put this into a sample app and add a PR that would be awesome! If not, I'm sure I'll get around to...
It sounds like this is not a decorator created with Nest's `createParamDecorator`, for controllers, resolvers, and gateways, but a general typescript decorator, is that correct?
Honestly, I would worry about testing a custom decorator via integration and e2e tests that use actual HTTP requests. If you do want to have an easy way to test...
Lots of changes I'm seeing! Most of them good. Can we stay away from the `feature/service/feature.service` directory structure though, and keep it as `feature/feature.service` the way it was?
> @jmcdo29 I'm still working on the example, I had a rough week :/ > Also - I'm planning to change the `Mockingbird` package API, can we wait with this...
An e2e test usually should be using a database, that way you are testing the entire flow, from the request coming in, to the data being saved, to the data...
@omermorad thanks for looking to continue! You can either use an in memory database, or you can add the mongo image to the docker-compose. Either way I look forward to...
Add a new `cats.e2e-spec.ts`. I'm pretty sure that's what the TypeORM sample does
Feel free to submit a draft PR. I've never made a wiki, but I thought it could be a decent place to explain some ideas of testing and go into...