Move user-facing string to template#26815
Merged
uranusjr merged 7 commits intoapache:mainfrom Oct 6, 2022
Merged
Conversation
bbovenzi
reviewed
Oct 3, 2022
dstandish
approved these changes
Oct 4, 2022
kaxil
approved these changes
Oct 4, 2022
ashb
approved these changes
Oct 4, 2022
Contributor
Author
|
@uranusjr Thanks for the merge! 😄 |
ephraimbuddy
pushed a commit
that referenced
this pull request
Oct 18, 2022
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com> (cherry picked from commit bab6dbe)
37 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This small PR just tweaks a single function, the single place it's called, and the template. It helps to separate out user-facing strings into templates for better MVC, and more concretely, for possible language translations in the future.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.