Conversation
|
@pokey Tests added. Some test or not currently possible. For example |
pokey
left a comment
There was a problem hiding this comment.
Nice! Haven't reviewed tests yet but overall looks like what we agreed on. Left a few comments
|
okay updated |
pokey
left a comment
There was a problem hiding this comment.
Yeah looking better. Few more minor comments then I'll have a look at the tests and we should be good to go!
sure happy to record the snippet ones. For "inside funk", we're actually looking for a scope type that doesn't have an "inside" to ensure that it doesn't expand to containing pair, right? I don't see why we can't test that today. Would just be an error test. Tbh would prob be better not to use "funk" because that will break when we support inside "funk". Maybe better to use "inside token"? |
|
I think I've added all the test I can now
|
Co-authored-by: Pokey Rule <755842+pokey@users.noreply.github.com>
Co-authored-by: Pokey Rule <755842+pokey@users.noreply.github.com>
This reverts commit 9ad7e9f.
| // NB: We import `Target` below just so that @link below resolves. Once one of | ||
| // the following issues are fixed, we can either remove the above line or | ||
| // switch to `{import("foo")}` syntax in the `{@link}` tag. | ||
| // - https://github.com/microsoft/TypeScript/issues/43869 | ||
| // - https://github.com/microsoft/TypeScript/issues/43950 | ||
| // eslint-disable-next-line @typescript-eslint/no-unused-vars | ||
| import type { Target } from "../../typings/target.types"; |
There was a problem hiding this comment.
Kind of annoying, but this was the best I could come up with cc/ @AndreasArvidsson @auscompgeek
Fixes #883
Fixes #882
Checklist