extract widget refactoring should use super-parameters where possible

[pq]

Extracting the Text widget here

class TestWidget extends StatelessWidget {
  const TestWidget({super.key});
  @override
  Widget build(BuildContext context) {
    return const Text('hi');
  }
}

yields

class TestWidget extends StatelessWidget {
  const TestWidget({super.key});
  @override
  Widget build(BuildContext context) {
    return NewWidget();
  }
}

class NewWidget extends StatelessWidget {
  const NewWidget({
    Key? key,
  }) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const Text('hi');
  }
}

but should produce:

class TestWidget extends StatelessWidget {
  const TestWidget({super.key});
  @override
  Widget build(BuildContext context) {
    return NewWidget();
  }
}

class NewWidget extends StatelessWidget {
  const NewWidget({
    super.key,
  });

  @override
  Widget build(BuildContext context) {
    return const Text('hi');
  }
}

if (at least) use_super_parameters is enabled.

Open question: and possibly just if the feature is available?

[bwilkerson]

I don't know what you mean by "available" or how that differs from "enabled", but I suspect that "enabled" is the correct thing to check.

[pq]

By available I was thinking of checking the SDK lower-bound but I think enabled is right. Thanks!

[bwilkerson]

Yes, you want to check enabled. A library can opt out of a feature while still having a lower bound that allows the feature to be used.