[MGNLRESTUI-73] Subapp name shows JSON gibberish Created: 11/May/23 Updated: 13/Dec/23 |
|
| Status: | Accepted |
| Project: | Magnolia REST Client UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| 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)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Epic Link: | RESTClient 2024 | ||||
| Team: | |||||
| Description |
|
When you open a detail subapp for an app based on REST-client-ui the browser subapp, the label of the subapp is the RAW json response. To a user it looks like the subapp label is broken. The REST-client-ui system should provide an easy way to set the label of the subapp based on the REST client response. |
| Comments |
| Comment by Scot Rhodes [ 11/May/23 ] |
|
It would be my expectation that a 'describeBy' property would be used to populate the label and page title, or possibly the 'jsonPathExpressions.itemId'. For example (based on the attached image), in the subApp's definition like this:
detail:
datasource:
$type: jsonDatasource
restClient: pc
restCall: claim
jsonPathExpressions:
itemId: '$.fields.policyNumber'
describeBy: '$.fields.policyNumber'
properties:
policyNumber: '$.fields.policyNumber'
policyHolder: '$.fields.policyHolder'
effectiveDate: '$.fields.effectiveDate'
expirationDate: '$.fields.expirationDate'
|