Skip to content

Update AV1137: Keep parameters as specific and narrow as possible #355

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 9, 2026
Merged

Update AV1137: Keep parameters as specific and narrow as possible #355

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c3821f2
Update AV1137 guideline
Mar 25, 2026
94c067d
Clarify AV1137 title to emphasize defining parameters
dennisdoomen May 9, 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/1137.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
rule_id: 1137
rule_category: member-design
title: Define parameters as specific as possible
title: Define parameters as specific and narrow as possible
severity: 2
---
If your method or local function needs a specific piece of data, define parameters as specific as that and don't take a container object instead. For instance, consider a method that needs a connection string that is exposed through a central `IConfiguration` interface. Rather than taking a dependency on the entire configuration, just define a parameter for the connection string. This not only prevents unnecessary coupling, it also improves maintainability in the long run.
Expand Down