• Add analyzer to guard against ToAsyncEnumerable VS AsAsyncEnumerable #37670
• N+1 detection (apparently Jetbrains are working on this).
• Internal usage analyzer: generic type argument for generic types (e.g. in instantiation)
• Add an analyzer for conventions #25022
• FindAsync + CancellationToken issue #12012
• Analyzer: warn (and code fix) for use of interpolation in SQL methods accepting raw strings #30965
• Analyzer to warn against accidental usage of AddEntityFrameworkProvider #25455
• Add an analyzer for new objects in OnConfiguring that are used as part of the ServiceProvider key #27856
• Analyzer suggestion: mark DbSet's nullability suppression property initializer as unnecessary #29988
• Analyzer: Unnecessary Configuration #11217
• Warn for use of nameof within raw SQL interpolated strings. This typically happens when people mistakenly want to interpolate column names, but they get parameterized and the query fails.

Scenarios requiring identifying EF Core LINQ queries (could use common infrastructure):

• Support ContainsKey (as an analyzer is telling us to use it) #26856
• Create DiagnosticSuppressor for CS8602 in Linq expressions and Includes #21663
• Translate int.Parse and similar #28287 (comment)
• Diagnostics analyzer for unnecessary Include #28449
• Analyzer warning and quick fix for ToDictionary over GroupBy #16838
• Analyzer to warn of final select that will retrieve entire entity because of client evaluation #37223 (closed for now, but see Query: Provide a way to indicate that part of a query should translate to server or throw #24509 which tracks doing more or less the same at runtime)

One idea here would be to have users tell us in .editorconfig that all queryable LINQ queries are e.g. SQL Server; this would be an opt-in that could unlock provider-specific warnings/code fixes.

See #20206 for previous unanalyzed scenarios.