Added new fields to post for translation service #47
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
vickyc2266
force-pushed
the
add-english-field
branch
from
9acb080
to
c916b09
Compare
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.
In public/openapi/components/schemas/PostObject.yaml and public/openapi/write/posts/pid.yaml, I added the fields isEnglish and translatedContent to the Post objects. This will enable the use of a translation service later on. I also created a new folder called translate, in which we can add more files for when we use an API.
Finally, I made some setup changes in files like .gitignore and .mocharc.yml to make working from this branch easier.