Anton Gilgur

If I have a type error in a declaration file, it doesn't error out and the build succeeds. Perhaps "forced to true" is incorrect wording then, instead it doesn't error...

Was debugging something else (`.jsx` support, c.f. https://github.com/jaredpalmer/tsdx/issues/523) and found that the [default `exclude` filter on the plugin](https://github.com/ezolenko/rollup-plugin-typescript2#plugin-options) is `exclude: [ "*.d.ts", "**/*.d.ts" ]` -- I still need to test...

So now that I know this codebase really well, I'm pretty sure that the problem is that rpt2 doesn't output diagnostics for any ambient types. I've renamed the issue as...

Ran into this from https://github.com/formium/tsdx/pull/719#issuecomment-683470971 where I could only tell from the Release Notes that `tslib`@2 was only compatible with TS 3.9+ as there is no peerDep listed. In https://github.com/formium/tsdx/pull/904#issuecomment-708283064...

`makedown` might be interesting since this library is similar to a Makefile written with Markdown

Superseded by #9980

The SDKs are autogenerated via OpenAPI. The OpenAPI spec should allow unset `finished_at`; if it doesn't, that is a fixable bug. If the SDK generation tools have a bug though,...

This was fixed by #10532 and #10599. Though there appear to be some lingering issues with Codespaces, see #11423 for follow-up bugs 😕

The example Workflow causes infinite recursion. Duplicate of #4180, #11499, #11497. There is a recursion depth limit now as of #11646, which effectively fixes this. There may be better detection...

I can't reproduce this in the current devcontainer (which I use quite frequently), so going to close this out as no longer an issue.