fix(deps): update dependency com.palantir.javaformat:palantir-java-format to v2#1836
Closed
renovate[bot] wants to merge 1 commit intomainfrom
Closed
fix(deps): update dependency com.palantir.javaformat:palantir-java-format to v2#1836renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Member
|
dupe of #1822 |
nedtwigg
deleted the
renovate/com.palantir.javaformat-palantir-java-format-2.x
branch
Contributor
Author
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.1.0->2.38.0⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
palantir/palantir-java-format (com.palantir.javaformat:palantir-java-format)
v2.38.0Compare Source
Automated release, no documented user facing changes
v2.37.0Compare Source
Automated release, no documented user facing changes
v2.36.0Compare Source
v2.35.0Compare Source
Automated release, no documented user facing changes
v2.34.0Compare Source
v2.33.0Compare Source
Automated release, no documented user facing changes
v2.32.0Compare Source
plugin.xmlmetadata file, but hopefully correctly this time.v2.31.0Compare Source
plugin.xmlmetadata file.v2.30.0Compare Source
No documented user facing changes
v2.29.0Compare Source
v2.28.0Compare Source
v2.27.0Compare Source
v2.26.0Compare Source
v2.25.0Compare Source
v2.24.0Compare Source
v2.23.0Compare Source
v2.22.0Compare Source
## Before this PR
Previous PR #707 was a little aggressive and inserted line breaks for non-statement lambdas.
## After this PR
Only multi-line lambdas cause a line-break in the method chain.
v2.21.0Compare Source
## Before this PR
Chained calls involving lambda expressions don't line break, which conflicts with checkstyle (at least the gradle-baseline checkstyle config)
java<br>class PalantirLambdaInliningPrefersBreak {<br> void foo() {<br> return hello.read(txn -> {<br> doSomeWork();<br> doSomeMoreWork();<br> })<br> .chainedCall(() -> {<br> doSomeWork();<br> });<br> }<br>}<br><br>## After this PR
java<br>class PalantirLambdaInliningPrefersBreak {<br> void foo() {<br> return hello<br> .read(txn -> {<br> doSomeWork();<br> doSomeMoreWork();<br> })<br> .chainedCall(() -> {<br> doSomeWork();<br> });<br> }<br>}<br>## Possible downsides?
🤷♂️ I've also added a test to show that non-chained lambda calls don't include a line break
v2.20.0Compare Source
Automated release, no documented user facing changes
v2.19.0Compare Source
v2.18.0Compare Source
v2.17.0Compare Source
v2.16.0Compare Source
v2.15.0Compare Source
Automated release, no documented user facing changes
v2.14.0Compare Source
v2.13.0Compare Source
v2.12.0Compare Source
v2.11.0Compare Source
PLUGIN_DIR/lib/*.jarstructure in addition to the oldPLUGIN_DIR/impl/*.jarlocationv2.10.0Compare Source
v2.9.0Compare Source
v2.8.0Compare Source
v2.7.0Compare Source
v2.6.0Compare Source
v2.5.0Compare Source
v2.4.0Compare Source
v2.3.0Compare Source
v2.2.0Compare Source
v2.1.0Compare Source
Collection<TextRange>toCollection<? extends TextRange>. This is inspired by same fix in bazel intellij plugin to avoid compiling multiple versionsv2.0.1Compare Source
v2.0.0Compare Source
* Break: Increase minimum source compatibility from java 8 to java 11.
* To use version 2.x of the formatter, you need to run on java 11 or higher.
* If you require the formatter to run on java 8, you won't be able to upgrade past version 1.x. Note that you can still produce java 8 jars from your repo but need to use at least java 11 to run the formatter.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.