Joe Pea

This is a great alternative to built-in extends (`is=""` attribute), but should be noted this doesn't cover the progressive enhancement use case. For example, if JavaScript is turned off (or...

This is interesting what it enables, but odd in how it does: certain features will be *runtime mixins* of a form that cannot be implemented in userland, basically. Can we...

It is also the case that mapped types get further in the way. For example, we actually may want to do this: ```ts declare module 'some-jsx-framework' { namespace JSX {...

`` \` `` for single back ticks perhaps. I don't think I've ever used or seen a single back tick anywhere, so a very few minority of people (if they...

I think a solution should work with both code fences, and `@example` blocks. Personally I think GitHub has the best handling of back ticks. Might be worth looking at. But...

[better-docs](https://github.com/SoftwareBrothers/better-docs) is a sweet JSDoc parser and generator for TypeScript, backward compatible with the original JSDoc. https://github.com/SoftwareBrothers/better-docs @wojtek-krysiak do you have any thoughts on how to handle decorators? I think...

JSDoc itself is still active, and the community has open issues for this: https://github.com/jsdoc/jsdoc/issues/1521 https://github.com/jsdoc2md/jsdoc-to-markdown/issues/209 @hegemonic do you have any opinions on decorator support? I believe we should all aim...

Decorators are non-experimental now with TypeScript 5. Can we have this fix soon pleeease? 🙏

@rnln I tried your suggestion, but that causes weird formatting for me: For now, this is what I've settled with my docs looking like: > (note, replace double ampersands with...

That snippet is working for me now. Not sure why I wasn't able to get it working before. EDIT: Ah, I was putting the invisible non-space *after* the `@`, not...