Skip to content

fix(deps): update rust crate structopt-utilities to ^0.1.0 - autoclosed#65

Closed
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/structopt-utilities-0.x
Closed

fix(deps): update rust crate structopt-utilities to ^0.1.0 - autoclosed#65
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/structopt-utilities-0.x

Conversation

@renovate

@renovate renovate Bot commented Sep 11, 2021

Copy link
Copy Markdown

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
structopt-utilities dependencies minor ^0.0.8 -> ^0.1.0

Configuration

📅 Schedule: "every weekend" (UTC).

🚦 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.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@github-actions

Copy link
Copy Markdown

Performance Regression Reports

commit: 4779afe

There are no regressions.

@renovate renovate Bot changed the title fix(deps): update rust crate structopt-utilities to ^0.1.0 fix(deps): update rust crate structopt-utilities to ^0.1.0 - autoclosed Sep 14, 2021
@renovate renovate Bot closed this Sep 14, 2021
@renovate renovate Bot deleted the renovate/structopt-utilities-0.x branch September 14, 2021 02:32
KSXGitHub pushed a commit that referenced this pull request May 13, 2026
Five new commits since `3ca7f01`:

- KSXGitHub/perfectionist#65 finishes `macro_argument_binding`'s
  non-expression-marker list. `looks_like_expression` now skips
  top-level `->` and `in` tokens alongside the `=` / `+=` / `:`
  / bare-operator markers added earlier. Resolves the residual
  case of the issue we filed as #416, where
  `tests::bytes_format::test_case!`'s
  `name -> value in system == expected` DSL was still flagged
  even after the `=` / `+=` fixes.
- KSXGitHub/perfectionist#67 introduces a crate-wide
  `[perfectionist]` config table with `enable` / `disable` arrays,
  and shifts `non_exhaustive_error`'s default state to
  `Disabled` (opt-in via `[perfectionist] enable =
  ["non_exhaustive_error"]`). This codebase already retired the
  rule in d845841, so the new upstream default matches our
  intent — no configuration needed.
- KSXGitHub/perfectionist#68, KSXGitHub/perfectionist#69,
  KSXGitHub/perfectionist#70 are documentation-only.

Drop the entire `[perfectionist::macro_argument_binding]
allow_extra` list. Every entry it carried — `bump`, `link`,
`make_const`, `symlink`, `test_case`, `visualize` — is now
silenced by the rule's own per-argument trivial-expression and
DSL-separator checks. Concretely:

- `bump!(items += 1)` — `+=` skipped (PR #52).
- `make_const!(LEVEL0_BLOCK = '█')` — `=` skipped (PR #52).
- `visualize!(tree, ())` — `tree` is a trivial path, `()` is the
  unit literal classified as trivial in PR #52.
- `link!("a" -> "b")` / `symlink!("a" -> "b")` — `->` skipped
  (PR #65).
- `test_case!(plain_number -> 65_535 in PlainNumber == "65535")`
  — `->` and `in` skipped (PR #65).

`deny_extra` stays as-is — the `assert_cmp::debug_assert_op*`
family still needs explicit denial so non-trivial arguments
inside them get caught.

https://claude.ai/code/session_01CoRidYHvni9nKNgxMPXmfQ
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