-
Notifications
You must be signed in to change notification settings - Fork 15
Support linting macros #142
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.
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
matthieucan
wants to merge
4
commits into
master
Choose a base branch
from
matthieucan/lint-macros
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| (content generated in CI) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| """Rules for dbt macros.""" | ||
|
|
||
| import re | ||
|
|
||
| from dbt_score import Macro, RuleViolation, rule | ||
|
|
||
|
|
||
| @rule | ||
| def macro_has_description(macro: Macro) -> RuleViolation | None: | ||
matthieucan marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| """A macro should have a description. | ||
|
|
||
| Macros are reusable code that should be well-documented so other developers | ||
| can understand their purpose and usage. | ||
| """ | ||
| if not macro.description: | ||
| return RuleViolation(message="Macro lacks a description.") | ||
|
|
||
|
|
||
| @rule | ||
| def macro_arguments_have_description(macro: Macro) -> RuleViolation | None: | ||
matthieucan marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| """All macro arguments should have a description. | ||
|
|
||
| From dbt Core v1.10+, macro arguments can be documented. This helps users | ||
| understand what parameters the macro expects and how to use them correctly. | ||
| """ | ||
| if not macro.arguments: | ||
| return None | ||
|
|
||
| invalid_args = [ | ||
| arg.get("name", "unknown") | ||
| for arg in macro.arguments | ||
| if not arg.get("description") | ||
| ] | ||
| if invalid_args: | ||
| max_length = 60 | ||
| message = f"Arguments lack a description: {', '.join(invalid_args)}." | ||
| if len(message) > max_length: | ||
| message = f"{message[:max_length]}…" | ||
| return RuleViolation(message=message) | ||
|
|
||
|
|
||
| @rule | ||
| def macro_name_follows_naming_convention(macro: Macro) -> RuleViolation | None: | ||
matthieucan marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| """A macro name should use snake_case naming convention. | ||
|
|
||
| Consistent naming conventions improve code readability and maintainability. | ||
| Macro names should use lowercase letters with underscores. | ||
| """ | ||
| # Check if name follows snake_case: lowercase letters, numbers, and underscores only | ||
| if not re.match(r"^[a-z0-9_]+$", macro.name): | ||
| return RuleViolation( | ||
| message="Macro name should use snake_case (lowercase with underscores)." | ||
| ) | ||
Oops, something went wrong.
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.