Drew Powers

This is awesome! Thanks so much for putting this together! > i am not familiar with the proper contribution workflow and probably i would mess up something so it's better...

That’s a great question, and thanks for asking! No one has really asked before 🙂. There are probably 2 main things to touch on: first the state of the API...

> now find myself wanting to do the opposite: having plugins consume files as input! Oh also forgot to address this specifically. I’m _hoping_ that by adding additional hooks to...

This is absolute gold! Thank you for taking the time to write all this up! ❤️. I’ll have to spend more time thinking about all your points. I can already...

After thinking about it a little more, the major difference between how Rollup works today and a Rollup-esque token workflow could work is [resolveId](https://rollupjs.org/plugin-development/#resolveid) behavior. In many examples, the source...

Chewed on all your great comments and thoughts, and I’m going to start formulating a 2.0 API for plugins. The DTCG is working on a 1.0 stable release of the...

Currently, openapi-typescript ignores `format` because in most instances it’s subjective how you’d want it interpreted. For example, for `{ "type": "string", "format": "date" }`, some may prefer it parsed as...

> The issue is that `key` could clash at runtime with any of the other fields. We'd need to define an enum consisting of all the keys of that type,...

Yeah I’m wondering if reverting to the old behavior of an intersection + a TS helper (or it sounds crazy, but maybe a union, depending on how it behaves in...

I’m all for better Intellisence and VS Code integration, but how would the runtime work? Would `client` have to be a getter method? And would this be able to use...