Joe Pea

Results 958 issues of Joe Pea

This is so awesome!!! _THIS_ is the proper direction TypeScript documentation should have gone in. The other solutions like `TSDoc`, `typedoc`, etc, are incompatible with the original `jsdoc` and hence...

Any thoughts on how to do it? I am thinking of a few options: 1. add ability to leafdoc to output to separate files, one per source file, so that...

I.e. why are they not scoped at the module level instead of at the class level? This means we can't use #private fields along with class-factory mixins. This works fine:...

I had code like the following, which worked great with `[[Set]]` semantics (f.e. in TypeScript with `useDefineForClassFields` set to `false`): ```js class Sub extends Node {...} const s = new...

Class-fields in TypeScript have `[[Set]]` semantics. Foresee code breaking when JavaScript projects convert to TypeScript (or vice versa), and the pain caused from hard-to-find bugs, because of JavaScript class-fields using...

The following should work, and it would mean that we can provide much better functionality: ```js class Foo { # x = 5 test() { console.log(this .# x) // it...

It would be convenient to get async stack traces, like what Chrome Devtools shows us in the sources tab. F.e. ```js // main.js function foo() { setTimeout(function bar() { const...

It'd be nice if we could get a stack traces without having to instantiate an Error (because sometimes we want a stack traces and instantiating an Error just for that...

issue: - https://github.com/solidjs/solid/issues/1810 (Don't forget to update this on Solid releases. Also pray that library authors stay up to date.)

@ryansolid mentioned that there are some gotchas with mutables, and we should document them. They [aren't mentioned](https://www.solidjs.com/docs/latest/api#createmutable). From [discord](https://discord.com/channels/722131463138705510/722131463889223772/978719976007557170): > there are just so many more considerations mutables bring and...

documentation