Allow changing translation engine from Echo to Nmt
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3
- Forks
- 2
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 3
Description
With the re-architecture of Serval, is it now possible for us to change a translation engine type from Nmt to Echo, and back again?
This will make it much easier for developers and testers of Scripture Forge, as we currently have to delete then recreate the engine - an action that deletes all builds associated with the engine.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating the Serval REST API entry point and the model or endpoint that updates a translation engine type. Done means an engine can switch between Nmt and Echo without deleting the engine or its associated builds, with coverage for both directions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100