Why this matters
Using `for` elements instead of `Map.fromIterable` improves readability and allows for compiler optimizations, making the code more performant.
Use `for` elements inside map literals instead of `Map.fromIterable` to improve readability and allow better compiler optimizations.
Using `for` elements instead of `Map.fromIterable` improves readability and allows for compiler optimizations, making the code more performant.
Side-by-side examples engineers can pattern-match during review.
Map<String, int>.fromIterable(
[1, 2, 3],
key: (v) => 'The value is $v',
value: (v) => v,
);{
for (final v in [1, 2, 3])
'The value is $v': v
}Map<String, int>.fromIterable(
[1, 2, 3],
key: (v) => 'The value is $v',
value: (v) => v,
);{
for (final v in [1, 2, 3])
'The value is $v': v
}From the same buckets as this rule.
All static JS/CSS/font/image files MUST use content-hashed filenames (e.g., app.9c1a7b.js) and be served with "Cache-Control: public, max-age=31536000, immutable". HTML and other non-fingerprinted documents MUST be served with "Cache-Control: no-cache" (or equivalent) to enable conditional revalidation.