Skip to content

Update AV1004: Use an interface rather than a base class to support multiple implementations #346

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

Merged
dennisdoomen merged 2 commits into from
May 10, 2026
Merged

Update AV1004: Use an interface rather than a base class to support multiple implementations #346

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fc01405
Update AV1004 guideline
Mar 25, 2026
b00477c
Update AV1004: remove mention of abstract default implementation
dennisdoomen May 10, 2026
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 _rules/1004.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,4 @@ rule_category: class-design
title: Use an interface rather than a base class to support multiple implementations
severity: 3
---
If you want to expose an extension point from your class, expose it as an interface rather than as a base class. You don't want to force users of that extension point to derive their implementations from a base class that might have an undesired behavior. However, for their convenience you may implement a(n abstract) default implementation that can serve as a starting point.
If you want to expose an extension point from your class, expose it as an interface rather than as a base class. You don't want to force users of that extension point to derive their implementations from a base class that might have an undesired behavior.