Review (Quiz)

A class should only depend upon a single interface

Every class should have just one responsibility

A sub-class should be able to replace any class without the program breaking

We should never create a sub-class from a base class

A sub-class should be able to replace any class without the program breaking

A sub-class should be able to replace its base class without the program breaking

We should prefer to use private class members wherever possible

We should create new features by extending entities, rather than modifying them

We should create new features by modifying entities, not extending them

We should depend on abstractions, not specific implementations

We should depend on specific implementations, not abstractions

Our entities should only depend upon a single abstraction

We should define a separate interface for every entity

Entities should not have to depend upon interfaces that they do not need

Interfaces should always be defined in separate files

They should not implement any logic

They should generally only communicate with the rest of the application through their inputs and outputs

They should use a service to communicate with the rest of the application

They can inject services and have broader knowledge of the goals of the application as a whole

They are generally the routed component

They should ONLY respond to events from child dumb components

routes, components, data-access, utils

feature, ui, data-access, utils

smart, dumb, data-access, utils

Everything should be shared by default

When it is used by multiple features in the application

As a last resort

utils

ui

component