Micael Levi L. Cavalcante

Results 257 comments of Micael Levi L. Cavalcante

@rubiin please share the steps to reproduce this using your repo https://github.com/rubiin/nest-swagger-bug `npm i && npm start` went fine so far 🤔

if we try to use https://repl.it, we'll get the same error. See https://replit.com/@micalevisk/trying-automapper#index.ts ![image](https://user-images.githubusercontent.com/13461315/171967069-a8447ff3-6fa2-49e6-9632-72f31c3c1502.png) But I guess this is due to how Repl.it builds the project. In this case, I'm...

![image](https://user-images.githubusercontent.com/13461315/148658408-e4d56b4e-836a-4123-b91c-8b85e270c5bb.png) just tested it on v2.0.0 & v2.1.1 :/ config.yml ```yaml defaults: preview: open: false width: 80 prSections: - title: Foo filters: is:open author:kamilmysliwiec ```

one way to validate that would be: ```js assert(message.content.length ?? message.images.length, number()) // Uncaught StructError: Expected a number, but received: undefined ``` another one: ```js assert(message.content ?? message.images, object({ length:...

The issue is that here: https://github.com/semantic-release/git/blob/09e00f98205e81e17ad9ec056a1efe20b42efb2a/lib/prepare.js#L37 isn't expected that `assets` could be `false`, as allowed here: https://github.com/semantic-release/git/blob/7756d6411d93228e77e56e6fb07944e04d343a58/lib/resolve-config.js#L6-L8 ![image](https://user-images.githubusercontent.com/13461315/152231312-14b5a4d4-b8c0-4c3a-b94b-6d5e5adc371b.png) A simple change like: ```diff - const filesToCommit = uniq( + const...

here's an up-to-date(?) fork: https://github.com/Aliheym/typeorm-transactional

what if you run ts-node with `--max-old-space-size` flag? `node -r ts-node/register --max-old-space-size=4096` this could be a memory leak tho.

So this following is expected to don't run inside transactions, right? ```js await getConnection() .createQueryBuilder() .insert() .into(User) .values([ { firstName: "Timber", lastName: "Saw" }, { firstName: "Phantom", lastName: "Lancer" }...

To me, using `export default` to identify the seeder class is pretty good. But I don't know what are the odds of relying on `default` property

> This link explain very well why. @jorgebodega got it. For now, you could add some note on README regarding this limitation. Something like: "Seeder files **must not** contain any...