[PUBLISHING-110] Return error codes from public instances in case of a failure Created: 24/Mar/21 Updated: 20/Jul/22 Resolved: 05/May/22 |
|
| Status: | Closed |
| Project: | Publishing |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Won't Do | 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)
|
| Date of First Response: | |
| Epic Link: | Nucleus Quality Maintenance |
| Team: |
| Description |
|
Publication is returning exception messages or i18nized error messages from public instance which may not tell the real reason why publication failed or. In some cases, messages even contain just null string without any explanation of what happened. Publication is doing checks based on the error messages returned from public nodes, which is wrong, especially if it's i18nized message which was translated. We could improve error handling by introducing error codes and error parameters for failures. Error codes would be translated on author and reported back to user either as a notification or a message. |
| Comments |
| Comment by Roman Kovařík [ 05/May/22 ] |
|
Closing this due to the amount of other more important tickets . Please reopen if needed. |