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

Stops optimizing imports via palantir-java-formatter #1089

Merged
merged 5 commits into from
May 21, 2024

Conversation

crogoz
Copy link
Contributor

@crogoz crogoz commented May 21, 2024

Before this PR

Optimizing imports via palantir-java-format is slow.
Previously (before switching to the new api: #1078), we would use Intelij's import optimizations (see: old implementation weren't overriding the optimizeImports implementation)

After this PR

We stopped doing the import optimization via the palantir-java-format. Now, it gets delegated to Intelij.

==COMMIT_MSG==
Stops optimizing imports via palantir-java-formatter
==COMMIT_MSG==

Possible downsides?

@changelog-app
Copy link

changelog-app bot commented May 21, 2024

Generate changelog in changelog/@unreleased

What 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 break and manual task changelog types will result in a major release!
  • 🐛 The fix changelog 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
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Stops optimizing imports via palantir-java-formatter

Check the box to generate changelog(s)

  • Generate changelog entry

@crogoz crogoz requested a review from CRogers May 21, 2024 15:39
@@ -95,6 +96,7 @@ public void tearDown() throws Exception {
}

@Test
@Disabled("Disabled the import optimization via palantir-java-format")
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd delete these tests entirely.

@@ -61,7 +61,7 @@ protected FormattingTask createFormattingTask(@NotNull AsyncFormattingRequest re

@Override
public @NotNull Set<Feature> getFeatures() {
return Set.of(Feature.FORMAT_FRAGMENTS, Feature.OPTIMIZE_IMPORTS);
return Set.of(Feature.FORMAT_FRAGMENTS);
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we return an empty set (or not override if it's set up like that) getImportOptimizers?

@bulldozer-bot bulldozer-bot bot merged commit 2fdb2c5 into develop May 21, 2024
7 checks passed
@bulldozer-bot bulldozer-bot bot deleted the cr/no-optimize branch May 21, 2024 16:03
@svc-autorelease
Copy link
Collaborator

Released 2.47.0

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.

4 participants