getbouncer / cardscan-android

Scan payment cards quickly and easily, including full number, name, and expiry.
MIT License
190 stars 34 forks source link

Bump ktlint from 0.41.0 to 0.46.0 #526

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps ktlint from 0.41.0 to 0.46.0.

Release notes

Sourced from ktlint's releases.

0.46.0

[0.46.0] - 2022-06-18

Promoting experimental rules to standard

The rules below are promoted from the experimental ruleset to the standard ruleset.

  • annotation
  • annotation-spacing
  • argument-list-wrapping
  • double-colon-spacing
  • enum-entry-name-case
  • multiline-if-else
  • no-empty-first-line-in-method-block
  • package-name
  • trailing-comma
  • spacing-around-angle-brackets
  • spacing-between-declarations-with-annotations
  • spacing-between-declarations-with-comments
  • unary-op-spacing

Note that as a result of moving the rules that the prefix experimental: has to be removed from all references to this rule. Check references in:

  • The .editorconfig setting disabled_rules.
  • KtLint disable and enable directives.
  • The VisitorModifier.RunAfterRule.

If your project did not run with the experimental ruleset enabled before, you might expect new lint violations to be reported. Please note that rules can be disabled via the the .editorconfig in case you do not want the rules to be applied on your project.

API Changes & RuleSet providers

If you are not an API user nor a RuleSet provider, then you can safely skip this section. Otherwise, please read below carefully and upgrade your usage of ktlint. In this and coming releases, we are changing and adapting important parts of our API in order to increase maintainability and flexibility for future changes. Please avoid skipping a releases as that will make it harder to migrate.

Lint and formatting functions

The lint and formatting changes no longer accept parameters of type Params but only ExperimentalParams. Also, the VisitorProvider parameter has been removed. Because of this, your integration with KtLint breaks. Based on feedback with ktlint 0.45.x, we now prefer to break at compile time instead of trying to keep the interface backwards compatible. Please raise an issue, in case you help to convert to the new API.

Use of ".editorconfig" properties & userData

The interface UsesEditorConfigProperties provides method getEditorConfigValue to retrieve a named .editorconfig property for a given ASTNode. When implementing this interface, the value editorConfigProperties needs to be overridden. Previously it was not checked whether a retrieved property was actually recorded in this list. Now, retrieval of unregistered properties results in an exception.

Property Ktlint.DISABLED has been removed. The property value can now be retrieved as follows:

astNode
    .getEditorConfigValue(DefaultEditorConfigProperties.disabledRulesProperty)
    .split(",")

and be supplied via the ExperimentalParams as follows:

ExperimentalParams(
    ...
    editorConfigOverride =  EditorConfigOverride.from(
</tr></table> 

... (truncated)

Changelog

Sourced from ktlint's changelog.

[0.46.0] - 2022-06-18

Promoting experimental rules to standard

The rules below are promoted from the experimental ruleset to the standard ruleset.

  • annotation
  • annotation-spacing
  • argument-list-wrapping
  • double-colon-spacing
  • enum-entry-name-case
  • multiline-if-else
  • no-empty-first-line-in-method-block
  • package-name
  • trailing-comma
  • spacing-around-angle-brackets
  • spacing-between-declarations-with-annotations
  • spacing-between-declarations-with-comments
  • unary-op-spacing

Note that as a result of moving the rules that the prefix experimental: has to be removed from all references to this rule. Check references in:

  • The .editorconfig setting disabled_rules.
  • KtLint disable and enable directives.
  • The VisitorModifier.RunAfterRule.

If your project did not run with the experimental ruleset enabled before, you might expect new lint violations to be reported. Please note that rules can be disabled via the the .editorconfig in case you do not want the rules to be applied on your project.

API Changes & RuleSet providers

If you are not an API user nor a RuleSet provider, then you can safely skip this section. Otherwise, please read below carefully and upgrade your usage of ktlint. In this and coming releases, we are changing and adapting important parts of our API in order to increase maintainability and flexibility for future changes. Please avoid skipping a releases as that will make it harder to migrate.

Lint and formatting functions

The lint and formatting changes no longer accept parameters of type Params but only ExperimentalParams. Also, the VisitorProvider parameter has been removed. Because of this, your integration with KtLint breaks. Based on feedback with ktlint 0.45.x, we now prefer to break at compile time instead of trying to keep the interface backwards compatible. Please raise an issue, in case you help to convert to the new API.

Use of ".editorconfig" properties & userData

The interface UsesEditorConfigProperties provides method getEditorConfigValue to retrieve a named .editorconfig property for a given ASTNode. When implementing this interface, the value editorConfigProperties needs to be overridden. Previously it was not checked whether a retrieved property was actually recorded in this list. Now, retrieval of unregistered properties results in an exception.

Property Ktlint.DISABLED has been removed. The property value can now be retrieved as follows:

astNode
    .getEditorConfigValue(DefaultEditorConfigProperties.disabledRulesProperty)
    .split(",")

and be supplied via the ExperimentalParams as follows:

ExperimentalParams(
    ...
    editorConfigOverride =  EditorConfigOverride.from(
      DefaultEditorConfigProperties.disabledRulesProperty to "some-rule-id,experimental:some-other-rule-id"
</tr></table> 

... (truncated)

Commits
  • d5c97e6 temporarily revert root build.gradle back to groovy (#1503)
  • 48fa886 Update CHANGELOG with 0.46.0 (#1502)
  • af18987 Filename should not be restricted to top level class declarations (#1500)
  • 1ce2b33 * Reformat to a multiline function signature when at least one parameter anno...
  • 550b761 Allow a function signature containing an EOL comment at the place of the para...
  • f19362c Ensure that rules in non-standard rulesets are prefixed with the rulesetId (#...
  • ec13516 Fix broken href links in README file (#1494)
  • 054d8c8 Adopt Kotlin 1.7.0 (#1490)
  • cb88ca1 Merge pull request #1488 from paul-dingemans/refactor-user-data
  • 5d2b29f Merge pull request #1487 from paul-dingemans/1029-suppress-in-file
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

Superseded by #528.