Mrthdrb

In most of the class's Constructors, a Context object is passed . I couldn't understand how this Context Obj works . I also noticed that sometimes this is passed to parent class's constructor like below.

public function __construct(
 MagentoFrameworkAppActionContext $context,
 MagentoCatalogModelDesign $catalogDesign,
 MagentoCatalogModelSession $catalogSession,
....
 parent::__construct(
 $context,
 $layoutFactory,

Can you please explain how this specific context object works ?

Note that there are different Context objects, in this case it's MagentoFrameworkAppActionContext and to understand it, you should read it as "ActionContext". It represents the application context in which the action is executed. In other words, it gives you access to all objects with application state that a controller action needs, for example the registry or the request object.

The context classes don't have own functionality, they are just a container for other objects. You can see them as shortcut to not have 20 parameters in each controller action. All common parameters are merged in the context object.

Context objects were introduced to isolate third party developers from changes in constructors of abstract classes.

In Magento 1 Abstract classes with a lot of "helper" behaviour were considered a convenient API for class extender. This caused huge numbers of methods and implicit dependencies in abstract classes (AbstractModel, AbstractBlock, AbstractAction)

In Magento 2 inheritance-based APIs (more precisely SPIs) are discouraged, but many legacy APIs still exist. Initially we planned to gradually remove extra behaviour from abstract classes. And to not break all extenders when we would remove some dependency from constructor, we introduced Context objects.

Current plan is to abandon inheritance-based APIs with interface-based APIs at some point.