Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Improve message when an automation step was not executed #19185

Merged
merged 2 commits into from
Dec 30, 2023

Conversation

emontnemery
Copy link
Collaborator

Proposed change

Improve message when an automation step was not executed

Type of change

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

Example configuration

Additional information

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

Checklist

  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • Tests have been added to verify that the new code works.

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

@emontnemery emontnemery added this to the 2024.1 milestone Dec 29, 2023
"no_further_execution": "This node was not executed and so no further trace information is available.",
"disabled_node": "This node was disabled and skipped during execution so no further trace information is available.",
"no_further_execution": "This step was not executed and so no further trace information is available.",
"disabled_step": "This step was disabled and skipped during execution so no further trace information is available.",
Copy link
Member

Choose a reason for hiding this comment

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

Can we keep the same keys, so the translations are not lost?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, but translations were added only 2 weeks ago and are not in a release yet, do we need to keep the keys? 🤔

Copy link
Member

Choose a reason for hiding this comment

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

They are probably already translates though, let me check

Copy link
Contributor

Choose a reason for hiding this comment

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

When you change the key of a translation, the old and new key of the translation are kept in localise. So, if it is already translated, the translation has to be redone. If it isn't, the translation needs to be translated twice. Next time, keep the key, then the translation is kept for history and doesn't need to be translated once or twice.

@bramkragten bramkragten merged commit 3c2fed5 into dev Dec 30, 2023
13 checks passed
@bramkragten bramkragten deleted the trace_step_not_executed branch December 30, 2023 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants