Kallen Tu comments

Results 10 comments of


Kallen Tu

proposal: `unintented_html_in_doc_comment`

Bumping this up again. If anyone has any objections, let us know. Otherwise, will try and see if I can work on this the upcoming week. cc @srawlins @pq

[doc_imports] `[this]` won't resolve to the current element in new analyzer comment resolver

Related linter issue: https://github.com/dart-lang/linter/issues/2079

[doc_imports] `[this]` won't resolve to the current element in new analyzer comment resolver

That sounds good. There's other ways to reference the current element anyways.

[doc_imports] Overridding members with no doc comments don't have resolvable references

cc @srawlins

New rendered text design for types and elements

> compute how long a signature is, in characters, which can be used in decisions to abbreviate with "..." or to use hard line splits, Could we perhaps just split...

`prefer_const_constructors` false positive for deferred elements

I think this should be fixed with https://github.com/dart-lang/sdk/commit/19859a0f9107c92649bf780aba5f4744b09d441f

[Wildcard Variables][spec] Late wildcard variables

Good call @eernstg. Didn't see that issue. Closing this one.

[wildcards] Late, wildcarded variables

Sounds like we'll probably let the **analyzer warn on late wildcard variables**. No changes needed for the spec. Closing for now. If we need more discussion on this, feel free...

[Wildcard Variables][spec] Allow `super._`?

cc. @dart-lang/language-team

use requirements and variations across all SDK tests

Linking Siggi's CL https://github.com/dart-lang/sdk/commit/5bf858c3603fff0d3fe44a5af06ec03f56f67a27 here for adding support for fine-grain requirements (variations) for my own reference.