dart-use-primary-constructors

To refactor a Dart class to use primary constructors, you move field declarations and initialization directly into the class header. This reduces boilerplate by applying concise syntax and managing initializer lists for Dart 3.13+ projects.

Primary constructors in Dart consolidate field declarations and initialization into the class header. They solve the problem of verbose traditional constructor syntax, reducing boilerplate and improving code readability for data models.

Primary constructor syntax requires Dart 3.13 or newer. You must upgrade your project environment to this version before refactoring legacy generative constructors into the concise primary constructor format.

The Primary Initializer Scope manages non-late field initializers within the class header. When using primary constructors, you must adhere to specific scoping rules to correctly differentiate between declaring and initializing parameters.

You should avoid primary constructors when working with Dart versions older than 3.13 or when your class requires complex initializer list logic that exceeds the abbreviated concise constructor syntax capabilities.

The best way to modernize Dart class constructors is migrating to primary constructors. This moves field definitions into the class signature, consolidating declarations and reducing boilerplate compared to traditional generative constructors.