Sometimes we need to limit access to class attributes so that it can be accessed only from the class itself. This concept is called **Encapsulation.**
Sometimes we need to limit access to class attributes, so that it can be accessed only from the class itself. This concept is called **encapsulation**.
In Dart we can make attributes **private** (meaning that they can be changed or used only in the instances of this class) by putting underscore (\_) in the beginning of fields' or methods' name.
Dart allows making attributes **private**, meaning that they can be accessed or modified from the class instance. Attributes are made private with a leading underscore (`_`) on the name of the method or attribute.
Bear in mind that in Dart there is no Encapsulation on a class level. According to Dart's documentation:
> But... There is no encapsulation at the `class` level in Dart. The encapsulation is rather applied at the scope of the library which contains the class.
- Importing libraries can help you create a modular and shareable code base. Libraries not only provide APIs, but are unit of privacy: private variables, i.e. starting with an underscore (\_) are visible only inside the library. Every Dart app is a library, even if it doesn’t use a library directive.
Importing libraries can help you create a modular and shareable code base. Libraries not only provide APIs, but are unit of privacy: private variables, i.e. starting with an underscore (`_`) are visible only inside the library. Every Dart app is a library, even if it doesn’t use a library directive.
Still, even on a class level it is a good practice to declare private values and not to use values that are intended to be private.
davhojt
2 years ago
committed by