Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Change wording and add examples for Liskov Substitution Principle #251
Conversation
|
Thanks for your expertise! You're right. Can you update your commit to not have the code example at the bottom. I like to keep the code examples only in a Good or Bad block |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Hello! Love this repo - incredibly useful, and I've bookmarked it for future reference.
I'd like to suggest a change to the writeup on the Liskov Substitution Principle. The text right now indicates that instances of a parent and child class can be used interchangeably. This is incorrect - the parent can be replaced by the child, but not the other way around. I've updated the wording and added a small illustrative example.
Thanks for maintaining this!