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

build(deps): bump go-simpler.org/sloglint from 0.5.1 to 0.6.0 #4645

Merged
merged 4 commits into from
Apr 20, 2024

Conversation

tmzane
Copy link
Contributor

@tmzane tmzane commented Apr 15, 2024

In continuation to #4512

Not sure about the new name, context does not seem descriptive to me. Maybe something like no-contextless? Weird, but easier to understand.

Please don't merge it yet, I'm going to update the pinned version later.

I've also improved the report message slightly.

go-simpler/sloglint@v0.5.1...v0.6.0

@tmzane tmzane marked this pull request as draft April 15, 2024 16:38
@ldez ldez self-requested a review April 15, 2024 17:59
@ldez ldez added dependencies Relates to an upstream dependency linter: update version Update version of linter go Pull requests that update Go code labels Apr 15, 2024
Copy link
Member

@ldez ldez left a comment

Choose a reason for hiding this comment

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

You should not modify:

  • .golangci.reference.yml
  • jsonschema/golangci.jsonschema.json

Also context-only should be removed from:

  • .golangci.next.reference.yml
  • jsonschema/golangci.next.jsonschema.json

I think context is good, at least less weird than no-contextless (IMHO it's not easier to understand)
The values can be improved, for example:

  • all -> always
  • scope -> existing

@ldez ldez added the feedback required Requires additional feedback label Apr 15, 2024
@tmzane
Copy link
Contributor Author

tmzane commented Apr 15, 2024

Also context-only should be removed from:

* `.golangci.next.reference.yml`

* `jsonschema/golangci.next.jsonschema.json`

If it is removed from the next version schema, won't it become illegal to use in the config? Thus, breaking backward compatibility with existing configs.

@ldez
Copy link
Member

ldez commented Apr 15, 2024

won't it become illegal to use in the config?

"illegal" no 😄

The JSON schema validation is only called explicitly, but the deprecation warning will always display, so everything will still work as expected.

@tmzane tmzane marked this pull request as ready for review April 20, 2024 16:53
@tmzane tmzane requested a review from ldez April 20, 2024 17:03
@ldez ldez removed the feedback required Requires additional feedback label Apr 20, 2024
Copy link
Member

@ldez ldez left a comment

Choose a reason for hiding this comment

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

LGTM

@ldez ldez merged commit 7ea621b into golangci:master Apr 20, 2024
13 checks passed
@ldez ldez added this to the next milestone Apr 20, 2024
@ldez ldez modified the milestones: next, v1.58 May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Relates to an upstream dependency go Pull requests that update Go code linter: update version Update version of linter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants