[EXCONTRANS-328] Refactoring Module Created: 22/Jan/20 Updated: 21/May/21 Resolved: 21/May/21 |
|
| Status: | Resolved |
| Project: | Content Translation Extended (CTX) |
| Component/s: | Core |
| Affects Version/s: | 3.0.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Teresa Miyar | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
Some refactoring could be done while using the DialogBasedPropertiesToTranslateFinder, we should provide the website or content app node while going through dialogs, that way we process the dialog fields with the corresponding properties or nodes as there are some complex items that create subnodes with properties i.e. multivalue using transformers. And the propertytotrasnlate should hold other values like the relative path. TranslationItemImporter should also be configurable by user. |
| Comments |
| Comment by Teresa Miyar [ 28/Feb/20 ] |
|
Must haves:
|