What is the correct order of calling superclass methods in initState, didUpdateWidget, dispose and other build methods? Why?

Question

In the Android development world there is a set order of Fragment/Activity lifecycle superclass method calls. I refer to the answer.

Now, regarding Flutter, if I type an empty StatefulWidget in IDE (both Visual Code and Android Studio) didUpdateWidget or any other callback, then I accept the prompt, I end up with such an order with place for implementation before the call.

  @override
  void didUpdateWidget(covariant AnimatedIconsCircle oldWidget) {
    // TODO: implement didUpdateWidget
    super.didUpdateWidget(oldWidget);
  }

The superclass method call order proposition is in contrary to the Flutter codebase:

  /// Implementations of this method should start with a call to the inherited
  /// method, as in `super.didUpdateWidget(oldWidget)`.
  @mustCallSuper
  @protected
  void didUpdateWidget(covariant T oldWidget) { }

What's the correct approach? Does it even matter?"

Answer 1

I realised that the docs are obvious about some of the build methods:

• https://api.flutter.dev/flutter/widgets/State/initState.html

Implementations of this method should start with a call to the inherited method, as in super.initState().

• https://api.flutter.dev/flutter/widgets/State/didChangeDependencies.html

No information. I tested it with InheritedWidget and the order doesn't matter.

• https://api.flutter.dev/flutter/widgets/State/didUpdateWidget.html

Implementations of this method should start with a call to the inherited method, as in super.didUpdateWidget(oldWidget).

• https://api.flutter.dev/flutter/widgets/State/dispose.html

Implementations of this method should end with a call to the inherited method, as in super.dispose().