Avoid wrapping fields in getters and setters just to be “safe”.

This rule is available as of Dart 2.0.0.

Rule sets: recommended, flutter

This rule has a quick fix available.


From Effective Dart:

AVOID wrapping fields in getters and setters just to be “safe”.

In Java and C#, it’s common to hide all fields behind getters and setters (or properties in C#), even if the implementation just forwards to the field. That way, if you ever need to do more work in those members, you can do it without needing to touch the callsites. This is because calling a getter method is different than accessing a field in Java, and accessing a property isn’t binary-compatible with accessing a raw field in C#.

Dart doesn’t have this limitation. Fields and getters/setters are completely indistinguishable. You can expose a field in a class and later wrap it in a getter and setter without having to touch any code that uses that field.


class Box {
  var _contents;
  get contents => _contents;
  set contents(value) {
    _contents = value;


class Box {
  var contents;


To enable the unnecessary_getters_setters rule, add unnecessary_getters_setters under linter > rules in your analysis_options.yaml file:

    - unnecessary_getters_setters