Morgan :)

Results 96 issues of Morgan :)

I heard rumour route is deprecated in favour of shelf -- is this the case? If so, a mention in the README would be good :) Thanks!

Pre-1.0 version numbers make it look like the package is not yet ready for use.

type-releasing

Pre-1.0 version numbers make it look like the package is not yet ready for use.

Per https://github.com/dart-lang/sdk/issues/32559 `MapEntry` does not implement `operator==` or `hashCode`; it would be useful to support it in `package:matcher`, e.g. default deep equals.

I don't have time to create a minimal repro right now, but writing this down so it doesn't get lost. It looks like an iterable that doesn't always return the...

Pre-1.0 version numbers make it look like the package is not yet ready for use.

status-blocked

Pre-1.0 version numbers make it look like the package is not yet ready for use.

next-breaking-release

I have an `analysis_options.yaml` using `include`: ``` include: package:dart_flutter_team_lints/analysis_options.yaml ``` And it looks correct because if I "dart analyze" I get findings: ``` info • lib/generate_dart_model.dart:141:15 • Method invocation or...

P1
area-analyzer
type-bug
triage-automation

I noticed that [ContextBuilder](https://github.com/dart-lang/sdk/blob/main/pkg/analyzer/lib/dart/analysis/context_builder.dart) currently passes through null `macroSupport` by default, with no way to provide one. (Unless you cast to `ContextBuilderImpl`). So people using the analyzer as a library...

area-analyzer
feature-macros

Filed for TODO in https://dart-review.googlesource.com/c/sdk/+/338440 modular_incremental_compilation.dart > Today I believe it is the case that we can compile different dart_library targets and re-use the old state, but these arguments are...

area-front-end
cfe-feature-macros
feature-macros