Skip to content

Conversation

@carterkozak
Copy link
Contributor

Before this PR

See palantir/safe-logging#515

After this PR

This change does two things:

  • The existing errorprone checks which reference preconditions
    have been updated to suggest the new package name
  • A new SafeLoggingPreconditionsMigration check has been added
    to automatically migrate code to the new package when a
    sufficiently new safe-logging version is available.
    ==COMMIT_MSG==
    Migrate preconditions to the new package
    ==COMMIT_MSG==

See palantir/safe-logging#515

This change does two things:
* The existing errorprone checks which reference preconditions
  have been updated to suggest the new package name
* A new `SafeLoggingPreconditionsMigration` check has been added
  to automatically migrate code to the new package when a
  sufficiently new `safe-logging` version is available.
@changelog-app
Copy link

changelog-app bot commented Jan 26, 2021

Generate changelog in changelog/@unreleased

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Migrate preconditions to the new package

Check the box to generate changelog(s)

  • Generate changelog entry

@policy-bot policy-bot bot requested a review from robert3005 January 26, 2021 20:23
@carterkozak carterkozak marked this pull request as draft January 26, 2021 20:23
@carterkozak carterkozak removed the request for review from robert3005 January 26, 2021 20:23
@carterkozak
Copy link
Contributor Author

Draft until palantir/safe-logging#515 is ready

@stale
Copy link

stale bot commented Feb 12, 2021

This PR has been automatically marked as stale because it has not been touched in the last 14 days. If you'd like to keep it open, please leave a comment or add the 'long-lived' label, otherwise it'll be closed in 7 days.

@stale stale bot added the stale label Feb 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants