Skip to content
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

upgrade golangci-lint to 1.52 #127

Merged
merged 2 commits into from
May 15, 2023
Merged

upgrade golangci-lint to 1.52 #127

merged 2 commits into from
May 15, 2023

Conversation

zeitlinger
Copy link
Member

@zeitlinger zeitlinger commented May 8, 2023

Based on #126

@zeitlinger zeitlinger requested review from rgeyer and mshahzeb May 9, 2023 12:57
@zeitlinger zeitlinger self-assigned this May 9, 2023
@@ -12,7 +12,7 @@ func newTargetRequiredMatcherRule(matcher string) *TargetRuleFunc {
name: fmt.Sprintf("target-%s-rule", matcher),
description: fmt.Sprintf("Checks that every PromQL query has a %s matcher.", matcher),
fn: func(d Dashboard, p Panel, t Target) Result {
// TODO: The RuleSet should be responsible for routing rule checks based on their query type (prometheus, loki, mysql, etc)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I presume that the TODOs were removed as a result of the updated linting? Can we override that rule?

All of the TODOs which were removed are still not complete, and.. I've been a poor maintainer in that they aren't tracked as issues either 🤦

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, we can override that rule - I'll do that

@rgeyer
Copy link
Collaborator

rgeyer commented May 12, 2023

One question on the TODOs. I approved pre-maturely assuming that this only upgraded the linter, without necessarily having any code changes.

@zeitlinger zeitlinger merged commit a502c1c into main May 15, 2023
7 checks passed
@zeitlinger zeitlinger deleted the lint branch May 15, 2023 08:33
gotjosh added a commit that referenced this pull request Aug 3, 2023
When attempting to get the configured unit of a panel, there's a chance that the field configuration is not on the dashboard definition. We should nil check this property before we attempt to access it.

Looks like this was introduced in #127
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants