James Garbutt
James Garbutt
### Which package(s) are affected? Other/unknown (please mention in description) ### Description Currently trying to get #3266 to pass tests. it will fail at runtime because of this: > The...
we now have a `@parse5/tools` package which provides the same functionality dom5 and various other helpers previously had. this is just a wip, trying to move lit over to using...
### Should this be an RFC? - [X] This is not a substantial change ### Description Finally having a look around the new analyzer to get a sense of its...
fixes #356 i need some help with the overloads here i think. you can see the strong types now mean a bunch of tests need to cast things too... im...
Currently many of the exported types are `any` or very weakly typed. It would be great if these types could be properly populated via the jsdoc. For example, the various...
Fixes #123 like i mention in the issue, i might add on to this to make `no-incompatible-type-binding` also take them into account. let me know if you think thats sensible
Consider this code: ```ts import {List} from '@material/mwc-list'; interface Foo { node: List; } // elsewhere... class MyElement extends LitElement { render() { return html``; } } ``` lit-analyzer will...
here's why i wanted runem/web-component-analyzer#165 the types are always `ANY` and i had to put the jsdoc the wrong way around (compared to anywhere else i saw it in the...
I have a feeling we're going to need this when we want to start detecting things like: ```html ``` It is very delicate right now in master because it depends...
if one of the lurkers finally reviews my parse5 types rewrite at DefinitelyTyped/DefinitelyTyped#48402, we can drop the workaround types here and use the official ones. draft until someone reviews the...