Skip to content

Correct LSP definition in acronym guide #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adamstz wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Correct LSP definition in acronym guide #124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion data/guides/cap-base-solid-kiss-what-do-these-acronyms-mean.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ The diagram below explains the common acronyms in system designs.
Units of code should be open for extension but closed for modification.

3. LSP (Liskov Substitution Principle)
A subclass should be able to be substituted by its base class.
A base class should be able to be substituted by its subclass.

4. ISP (Interface Segregation Principle)
Expose multiple interfaces with specific responsibilities.
Expand Down
Loading