Auke van Leeuwen

> 🤔 can you confirm this text is printed out in the scenario on your side too? Trying not to hijack the thread here, but just wanted to confirm I...

(disclaimer: not a contributor, actually first time user). I'm not sure _how_ you view the request body, just wanted to mention that I also didn't see the request body when...

Thanks for your quick response, and the library in general. > We publish all the modules of this library in UMD so that they can be used in both Nodejs...

@whimzyLive, no worries. I did have a look at it, but have no experience with your build system. [Your `tsconfig` looks reasonable](https://github.com/typedorm/typedorm/blob/72fb5094c2201373dcc5dfec47f9308637ee44b2/tsconfig.json#L14). But apparently somewhere in the Bazel build system...

👋 hello, I'm having a bunch of false positives (IMHO) on TypeScript code. I figured I could fix the rule myself and I did in this PR. The build is...

Just adding some thoughts to this thread as well: the change to `any` is a bit unfortunate for us. We use this pattern quite a lot: ```typescript expect(something).toEqual({ // ......

@keeganwitt Right, this issue got a bit off my radar, but since updating to the version that included https://github.com/jest-community/jest-extended/pull/535, it popped up again :-) For us - for most cases...

I cannot give an exhaustive list of things that are giving warnings (but are still working), but at the very least `coverageDirectory`: ``` ● Validation Warning: Unknown option "coverageDirectory" with...

Same, even the word `Authorization` (as the value of the API key *name*) is too much. ``` 2055 | "ApiKeyName": "Aut**********", ``` Worse though: I don't know how to turn...

👊 I could use this as well @jamesdbloom :-) A release would be nice since I don't see another way of overriding it to v1.3. It's rather hard coded.