This tutorial is intended to create a simple Angular app which drives a “common issue in OOP paradigm” which is code duplication and hidden patterns usually found in real world that can be solved using Inversion of Control techniques and allowing us to perform declarative programming.
 User dialog format/content isn’t part of tutorial’s scope
 Error dialog format/content isn’t part of tutorial’s scope
Users (writers) resource is placed here: https://jsonplaceholder.typicode.com/users
Posts resource is placed here: https://jsonplaceholder.typicode.com/posts
You can follow these instructions, step by step.
Prepare your workspace
$ git clone https://github.com/k1r0s/angular2-srp-showcase.git
$ git checkout normal-oop
$ npm install
Run the code
$ npm start
Read the code
Okay so lets start by opening
src/app/components/writers/writers.component.ts . This component has the following responsibilities:
Now lets look over
src/app/components/user-posts/user-posts.component.ts . This one has the following responsibilities:
Most of times a method body that should describe a business action is entangled with code that does not describe at all that action. Like opening a dialog, capturing exceptions, subscribe to close events, etc.
In OOP we try to separate concerns by declaring entities (classes) that group actions (methods) that describe what business wants to happen and where (domain speaking). Methods describe how things should be fulfited.
A common issue in OOP paradigm is that, to replicate a behavior, code must be replicated too. Sometimes class extension isn’t enough because your behavior doesn’t always occur in the same spot or you simply don’t have enough time to change whole app arquitecture. For example, a log service has to be invoked at the end of some method calls printing method’s arguments and result but that implementation isn’t important at all in terms of domain problem meaning that code is polluting your app. Can you deal with logs calls with class extension? nope.
What about projects with 12 developers coding the same behavior with different implementation? That’s hidden patterns. For example when a developer is used to add a feature similar or identical a previous one most of them will seek that previous implementation on the code base to look ‘how to deal with the same problem’ or simply paste that code in their feature changing some variables related with the context of that specific screen or feature, while some developers will implement their own code to solve the same problem. We don’t care about which implementation is the best. Different implementations for the same problem drives bugs, code is harder to mantain, etc. An easy solution to deal with this are interface definition that all developers must agree. But still duplication spreads.
Authentication, Ajax resolution, UX action invocation, exception handling… almost anything that isn’t related with business logic its likely to be invoked in several places and that implementations can pollute your domain logic.
Lets back to writers component
What is really doing
writers.component.ts at setup ?
Many concerns take place as this code gets executed. In terms of domain this is simply fetch and render users list. There are a few domain rules that apply on this, catch resources, show a loading dialog while requesting a resource…
That behavior also gets replicated on
user-posts.component.ts . But on this case there is a domain concern before: grab the selected user from cache.
There is a way to code that implementation abstracting us from component’s specific domain? Yes!
We already defined some interfaces that
LoadingDialog, ResourceContainer<T>, LoadingDialog, CacheContainer . We also assure that there are no hidden patterns.
Hence we can achieve this on both components:
Note that the same behavior needs to be invoked in different spots and with different context/arguments.
And this works, trust me (running example).
argsDriverIndex param for
@ArgsCacheReader its just a specification of which method arguments index will be used as a serialized key to read/write from cache. This means that
user-posts.component.ts will access cache having first
fetchPostsargument. Therefore it will not call the same resource twice.
Is important to know that these decorators can be imported everywhere and are completly standalone (that depends on you). Meaning that you can remove some of them without messing callstack while in common OOP implementations you face side effects.
Method and class Decorators are a powerful tool against repetition and, it also provides a needed abstraction layer needed in modern applications. We have cleared infrastructure code from our component by using declarative programing whichs aims for:
Our code is clear as water and easy to mantain.
We have to understand that we have created a strong association with two components which can become very different in the near future. So if our abstraction is somehow deprecated, we must remove this decorator from that component which no longer match a pattern (interface), paste its implementation and code the difference.
Decorators are bread and butter in modern libraries like Angular, Vue (addon), also in backend, for instance Nest framework provides a lot of built in decorators to enhace your dev experience, improve readability, separate concerns.. etc.
Decorators are nice because provide you a language feature that allows you to add/remove/manage rich implementations without messing in language primitives.
Maybe in the near future decorators will be used as “standalone plugins” which can be downloaded and plugged in your code providing features (example).
For instance, Angular’s
@Component decorator is a neat way to register your class as a web component into angular boilerplate. So why you wont define some for your own needs?
Babel does not support interfaces to deal with hidden patterns, but it supports method and class decorators.
I created a library that makes very easy define your own method/class decorators. It will allow you to change, extend, modify the behavior of methods and constructors non-invasively. Of course this tutorial example was made using that library.
Give a try!