Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Prevent trailing line feeds in translation values #126446

Merged
merged 2 commits into from
Sep 23, 2024
Merged

Prevent trailing line feeds in translation values #126446

merged 2 commits into from
Sep 23, 2024

Conversation

epenet
Copy link
Contributor

@epenet epenet commented Sep 22, 2024

Proposed change

SSIA

Follow-up to #126427

cc @MartinHjelmare, based on post-merge feedback in #126427 (comment)

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

@home-assistant home-assistant bot added cla-signed code-quality small-pr PRs with less than 30 lines. labels Sep 22, 2024
@epenet epenet marked this pull request as ready for review September 22, 2024 18:55
@@ -12,7 +12,7 @@
"description": "[%key:component::bluetooth::config::step::bluetooth_confirm::description%]"
},
"reauth_confirm": {
"description": "The activation code is no longer valid, a new unused activation code is needed.\n\n"
"description": "The activation code is no longer valid, a new unused activation code is needed."
Copy link
Contributor Author

Choose a reason for hiding this comment

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

As with all other violations, the line feeds seem intentional - but I am unsure why.

Copy link
Member

Choose a reason for hiding this comment

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

It doesn't seem valid. If we want blank lines after the description in the UI that should be handled by the frontend, consistently.

Copy link
Contributor

@allenporter allenporter left a comment

Choose a reason for hiding this comment

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

I may have added this for the google ones (which were copied to the others) but i'm not seeing an immediate reason.

There doesn't appear to be extra whitespace in the rendered markdown in an existing production instance:

Screenshot 2024-09-22 at 12 02 57 PM

I have not tried it with this change, but assuming it looks the similar then this seems fine to me.

@joostlek joostlek merged commit fb400af into dev Sep 23, 2024
44 checks passed
@joostlek joostlek deleted the epenet-patch-1 branch September 23, 2024 11:02
@github-actions github-actions bot locked and limited conversation to collaborators Sep 24, 2024
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
cla-signed code-quality small-pr PRs with less than 30 lines.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants