Skip to content

Say in the README that the CLI has no style flag - #85

Merged
abashev merged 1 commit into
mainfrom
readme-no-style-flag
Sep 26, 2026
Merged

abashev merged 1 commit into
mainfrom
readme-no-style-flag

Conversation

@abashev

@abashev abashev commented Sep 26, 2026

Copy link
Copy Markdown
Collaborator

Before this PR

The palantir-to-open table in the README pairs --palantir with --ojf and -ojf, as if the command
line still needed a style flag. It has not since 2.98.0.2: it formats in the one style without a flag.

After this PR

==COMMIT_MSG==
The README says the command line has no style flag. --ojf and -ojf are only accepted for old
scripts: the formatter prints a warning to remove them and formats as usual, while --palantir
stops it with exit code 2. The row uses the words of the site's Migrate page, "none: there is one
style".
==COMMIT_MSG==

Checked with the 2.98.0.4 command line. The site already says the same on Migrate and Command line;
nothing else in the repository's docs names a style flag.

Possible downsides?

None: the row only describes what the command line has done since 2.98.0.2.

The palantir-to-open table still paired --palantir with --ojf and -ojf,
but since 2.98.0.2 the command line formats in the one style without a
flag. --ojf and -ojf are only accepted for old scripts: the formatter
prints a warning to remove them and formats as usual, while --palantir
stops it with exit code 2. The row now says there is no flag, in the
words the site's Migrate page uses.

Checked with the 2.98.0.4 command line.
@abashev
abashev merged commit 1a01c3b into main Sep 26, 2026
16 checks passed
@abashev
abashev deleted the readme-no-style-flag branch September 26, 2026 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant