Skip to content

Conversation

@Moyf
Copy link
Contributor

@Moyf Moyf commented Sep 15, 2025

No description provided.

Moyf added 6 commits September 2, 2025 11:09
* feat(settings): add option to hide notice when no change

Introduce a new setting noNoticeWhenNoChange to control whether the
post-lint notice is shown when no characters are added or removed.

- Add noNoticeWhenNoChange to settings data and default values, with
  comments.
- Persist and normalize the setting during loadSettings to ensure a
  boolean default.
- Add a ToggleSetting in the General tab UI and include localization
  entries (en, zh-cn) for name and description.
- Update displayChangedMessage to respect the new setting and skip
  showing the notice when no chars were added/removed.

This reduces noise for users who prefer no feedback when linting makes
no effective changes.

* feat(locale): add more translations

- Translated by AI

* refactor: rename variable name

Update settings, usage and translations to use a clearer name for the
option that suppresses messages when there are no actual changes.

- Rename settings property in loadSettings from noNoticeWhenNoChange to
  suppressMessageWhenNoChange and default it to false.
- Update displayChangedMessage to read suppressMessageWhenNoChange and
  skip message emission when chars added + removed is zero.
- Update translation keys and copy in ru, tr, de, es locales from
  no-notice-when-no-change to suppress-message-when-no-change and adjust
  wording to match the new name.
- Remove a now-duplicate UI setting block in general-tab that created
  the old toggle for noNoticeWhenNoChange (the UI now uses the renamed
  setting elsewhere).

This clarifies intent (suppress message vs. no notice) and consolidates
the implementation to the new, consistent setting name.
Adjust the constructor call and remove stray whitespace in the general
tab component to match expected parameter formatting.

- Remove an extra blank character left after a conditional block.
- Add a missing trailing comma for the plugin argument in the
  ToggleSetting constructor call to ensure consistent argument
  separation and avoid potential lint/format issues.

These small fixes improve code style consistency and prevent minor
syntax/formatting problems in the UI linter component.
@Moyf Moyf closed this Sep 15, 2025
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