DetachHead comments

Results 929 comments of


                                            DetachHead

support multiple config files in the language server

actually i think this should be supported, since `executionEnvironments` has a different use case (see #668) and they don't support the use case of having different `excludes` (like the example...

`deprecated` decorator should work with messages that are `Literal` or `LiteralString`

in library mode/cringe mode (#539) it should report an error if you try to do this though, because it wouldn't work for downstream users if they aren't using basedpyright as...

`deprecated` decorator should work with messages that are `Literal` or `LiteralString`

https://github.com/DetachHead/basedpyright/issues/539#issuecomment-2330663351

`expect` functions should be typed

@jakemac53 thanks! is there an issue tracking the progress of the new library? if so i can close this issue

`expect` functions should be typed

i get that, thought imo that's an edge case you can easily work around by explicitly specifying the generic: ```dart checkThat(1).equals(''); ```

`reportPossiblyUnboundVariable` false negative on assignments to instance attribute

maybe related?: #682

support narrowing on `a is b` where `b` is a generic

related: #391

`reportUnannotatedClassAttribute` false positive on non-declarations

we should probably just switch to having `reportIncompatibleUnannotatedOverride` enabled by default instead. i've been using it for ages and haven't noticed any performance issues with it

`reportUnannotatedClassAttribute` false positive on non-declarations

i don't remember why i called it that. `reportUnannotatedAttribute` probably would've been a better name

`reportUnannotatedClassAttribute` false positive on non-declarations

`reportUnannotatedClassAttribute` and `reportIncompatibleUnannotatedOverride` are just two different solutions to the same problem: ```py from typing import reveal_type class Foo: def __init__(self, bar: str) -> None: self.bar = bar # error...