@internaland have an appropriate comment in the docblock why they should not be used or decorated directly.
@internalneed not be kept compatible for third-party developers. Here the public api can change at any time.
__constructmethods of services instantiated via DI container are not public API and can be changed at any time
__constructfunctions of Data Transfer Objects (DTO), which could therefore be instantiated by the developer himself (e.g.
QuantityPriceDefinition), are public API and must be kept backward compatible