Add source and target refs to Pretranslations and WordAlignments #863
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.
Fixes #806
I know this won't get into the release today but I wanted to at least push my work and get the review process started since it was slated for this sprint.
There are a lot of options regarding where to keep the
refsproperty and where to replace it (e.g., do we migrate the db?). The work currently on this branch removes the generic ref property from the machine engine side of things, but still allows old pretranslations to be properly deserialized from the bucket and keeps the refs property in the model (just adding source and target ref properties and giving them preference when utilizing them on the usfm endpoint). I've also deprecated the refs property in the dto.This change is