refactor: Mark semantically final variables as final (or const) proper [DCM] (#2783)

I was playing around with the rule avoid-global-state
While I don't think we should enable it, because we do have several totally legitimate cases of what the rule considers global state, it did help me find any current cases where the things just should be final constants.
So this PR will mark semantically final variables as final (or const) proper, exclusively on examples (no violations on actual src code are legit).
This commit is contained in:
Luan Nico
2023-10-02 03:45:42 -04:00
committed by GitHub
parent a036f19517
commit 71f7b475e3
8 changed files with 15 additions and 14 deletions

View File

@ -4,8 +4,8 @@ import 'package:flame/text.dart';
import 'package:flutter/painting.dart';
class RichTextExample extends FlameGame {
static String description = 'A non-interactive example of how to render rich '
'text in Flame.';
static const String description =
'A non-interactive example of how to render rich text in Flame.';
@override
Color backgroundColor() => const Color(0xFF888888);