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

Removing Feature.AD_HOC_FORMATTING from PalantirJavaFormatFormattingService #1083

Merged
merged 4 commits into from
May 2, 2024

Conversation

crogoz
Copy link
Contributor

@crogoz crogoz commented May 2, 2024

Before this PR

In #1078 we switched to the new Formatting APIs following google-java-format's commit: google/google-java-format@84b2c9a
However, this broke the Intelij generation code - see:

new generated code after extracting code:
wrong

expected code after extracting code:
correct

After this PR

Removing Feature.AD_HOC_FORMATTING from PalantirJavaFormatFormattingService . The flag was remoced from google-java-format as well in a later PR: google/google-java-format@25ce685

==COMMIT_MSG==
Remove AD_HOC_FORMATTING
==COMMIT_MSG==

Possible downsides?

Fixes #1080

@changelog-app
Copy link

changelog-app bot commented May 2, 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

Fixes bug where generated code or automated refactoring is formatted incorrectly by removing AD_HOC_FORMATTING

Check the box to generate changelog(s)

  • Generate changelog entry

@crogoz crogoz changed the title no ad_hoc_formatting Removing Feature.AD_HOC_FORMATTING from PalantirJavaFormatFormattingService May 2, 2024
@@ -0,0 +1,5 @@
type: fix
fix:
description: Removing Feature.AD_HOC_FORMATTING from FormattingService
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably best to describe the change in terms of what the user cares about - I'd say something like "fixes bug where generated code or automated refactoring is formatted incorrectly by removing AD_HOC_FORMATTING"

@CRogers
Copy link
Contributor

CRogers commented May 2, 2024

👍🏻

@bulldozer-bot bulldozer-bot bot merged commit 95485b2 into develop May 2, 2024
7 checks passed
@bulldozer-bot bulldozer-bot bot deleted the cr/fix-formatting- branch May 2, 2024 15:42
@svc-autorelease
Copy link
Collaborator

Released 2.46.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.

Intellij plugin: missed newlines on IDE auto-completion
4 participants