However, changing or restricting the types of method signatures or classes using decorators isn’t possible yet. You can also store initialization logic for the decorated field. Therefore, (method/class) name, visibilities, and arguments are also available. Implementing a decorator is based on an interceptor. This can come from a separate method call or even an HTTP API call.
One example is enriching the return data with additional information. This can refer to both calling the method (a cache, for instance) and its return. In contrast to the proxy pattern, this isn’t about controlling access to a method, but extending the method’s behavior with added functionality. To help you understand, imagine that the name “decorator” is derived from the classic “Gang-of-Four” decorator pattern. Generally, decorators are a way to implement repetitive aspects and apply them in multiple places.
