Interfaces and Service Contracts

interface usage interfaces are used for many models, services and validators where it may be beneficial to application integrating the sdk to replace functionality entirely, or implement alternative / additional versions (such as with validators or providers) replacing a concrete implementation of an interface should be avoided if possible; if necessary, the native class should be extended rather than replaced entirely dependency injection should be used to replace the smallest possible component to enable customisations, especially in composite classes such as the useragentprovider service contracts interface will often be found as close to the aplicable implementations as possible, many times in the same folder an exception to this is the root api directory, which defines contracts for the primary models and services used in the php sdk package interfaces within the api directory as well as classes tagged @api should be considered stable within the major version in which they appear this means that the class will not be removed or have its method signatures changed without bumping the major version of the application (eg from 1 x to 2 x) this includes the addition of new methods or interfaces note, changes to non api classes will still occur within minor and, occasionally, patch releases this may include adding new classes / methods / optional arguments in public methods any potentially breaking changes will always accompany a major version upgrade this may include removing classes or methods, or adding new mandatory arguments to existing public methods