Add translation resources to support recipe problem-reporting functionality #23
Conversation
This file contains 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.
Describe the reason for these changes and the problem that they solve
As described in openculinary/frontend#272 we currently anticipate three workflows that users may want to use to report problems with recipes that appear in our search results (removal requests, unsafe content reports, and corrections).
This changeset adds the translation resource strings that will be used for the user-facing functionality.
Briefly summarize the changes
How have the changes been tested?
List any issues that this change relates to
Relates to / supports openculinary/frontend#272.