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

Fix issue where formatter is not always enabled on save in intellij #1110

Conversation

CRogers
Copy link
Contributor

@CRogers CRogers commented Jul 30, 2024

Before this PR

We've had sporadic reports of the formatter not being enabled on save in intellij. I ran into this yesterday and today.

After this PR

==COMMIT_MSG==
The formatter should now always been enabled on save in intellij.
==COMMIT_MSG==

Possible downsides?

@changelog-app
Copy link

changelog-app bot commented Jul 30, 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

The formatter should now always been enabled on save in intellij.

Check the box to generate changelog(s)

  • Generate changelog entry


def myAllFileTypesSelectedAlreadySet = matchChild(onSaveOptions, 'option', [name: 'myAllFileTypesSelected'])
.map { Boolean.parseBoolean(it.attribute('value')) }
.orElse(true)
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is the crux of the bug. If myAllFileTypesSelected did not already exist, we would think it is already set to true and make no further changes, despite the default being false.

svc-changelog and others added 3 commits July 30, 2024 13:49
…led' of github.com:palantir/palantir-java-format into callumr/fix-issue-where-formatter-is-sometimes-not-enabled
@@ -183,8 +177,7 @@ class ConfigureJavaFormatterXmlTest extends Specification {
def node = new XmlParser().parseText """
<root>
<component name="${action}OnSaveOptions">
<option name="myRunOnSave" value="true"/>
<!-- if myAllFileTypesSelected does not exist, it defaults to true -->
Copy link
Contributor Author

Choose a reason for hiding this comment

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

lies

@felixdesouza
Copy link

👍

@bulldozer-bot bulldozer-bot bot merged commit 9b4e150 into develop Jul 30, 2024
7 checks passed
@bulldozer-bot bulldozer-bot bot deleted the callumr/fix-issue-where-formatter-is-sometimes-not-enabled branch July 30, 2024 14:45
@svc-autorelease
Copy link
Collaborator

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