initServiceExtensions method

  1. @override
void initServiceExtensions()
override

Called when the binding is initialized, to register service extensions.

Bindings that want to expose service extensions should overload this method to register them using calls to registerSignalServiceExtension, registerBoolServiceExtension, registerNumericServiceExtension, and registerServiceExtension (in increasing order of complexity).

Implementations of this method must call their superclass implementation.

A registered service extension can only be activated if the vm-service is included in the build, which only happens in debug and profile mode. Although a service extension cannot be used in release mode its code may still be included in the Dart snapshot and blow up binary size if it is not wrapped in a guard that allows the tree shaker to remove it (see sample code below).

The following code registers a service extension that is only included in debug builds.
link 
void myRegistrationFunction() {
  assert(() {
    // Register your service extension here.
    return true;
  }());
}

A service extension registered with the following code snippet is available in debug and profile mode.
link 
void myOtherRegistrationFunction() {
  // kReleaseMode is defined in the 'flutter/foundation.dart' package.
  if (!kReleaseMode) {
    // Register your service extension here.
  }
}

Both guards ensure that Dart's tree shaker can remove the code for the service extension in release builds.

See also:

Implementation

@override
void initServiceExtensions() {
  super.initServiceExtensions();

  if (!kReleaseMode) {
    registerNumericServiceExtension(
      name: SchedulerServiceExtensions.timeDilation.name,
      getter: () async => timeDilation,
      setter: (double value) async {
        timeDilation = value;
      },
    );
  }
}