gradle-baseline
gradle-baseline copied to clipboard
ResourceIdentifierGetEqualsUsage
Before this PR
After this PR
==COMMIT_MSG==
ResourceIdentifierGetEqualsUsage rewrites code using ResourceIdentifier#get*().equals(Object) to ResourceIdentifier#has*(String) to avoid allocations. See https://github.com/palantir/resource-identifier/pull/423
==COMMIT_MSG==
Possible downsides?
Generate changelog in changelog/@unreleased
changelog/@unreleasedWhat do the change types mean?
feature: A new feature of the service.improvement: An incremental improvement in the functionality or operation of the service.fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.break: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations).deprecation: Advertises the intention to remove service functionality without any change to the operation of the service itself.manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed.migration: A fully automatic upgrade migration task with no engineer input required.
Note: only one type should be chosen.
How are new versions calculated?
- ❗The
breakandmanual taskchangelog types will result in a major release! - 🐛 The
fixchangelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.
Type
- [ ] Feature
- [x] Improvement
- [ ] Fix
- [ ] Break
- [ ] Deprecation
- [ ] Manual task
- [ ] Migration
Description
ResourceIdentifier#get*().equals(Object) to ResourceIdentifier#has*(String) to avoid allocations. See https://github.com/palantir/resource-identifier/pull/423
Check the box to generate changelog(s)
- [x] Generate changelog entry
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.
✅ Successfully generated changelog entry!
What happened?
Your changelog entries have been stored in the database as part of our migration to ChangelogV3.
Need to regenerate?
Simply interact with the changelog bot comment again to regenerate these entries.
Released 6.53.0