[MGNLUI-4244] Implement new VirtualUriMapping app against registry API Created: 07/Jul/17  Updated: 11/Mar/21  Resolved: 11/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Oanh Thai Hoang Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLUI-4313 Demote About app's VirtualUriMapping ... Closed
Relates
supersession
supersedes MAGNOLIA-3349 Port Virtual URI mappings to a Registry Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Virtual URI mappings

 Description   
  • Compare w/ definitions app, filtering by the registry type
    • Do we see enough information? The dedicated table with columns from that subapp is probably clearer, UI-wise.
  • In info.magnolia.about.app.mapping.VirtualURIMappingViewImpl
    • Replace VirtualURIManager with info.magnolia.virtualuri.VirtualUriRegistry
  • Consider Updating the whole subapp to a ToolsSubApp?
    • like Security app's permissions tool


 Comments   
Comment by Roman Kovařík [ 11/Mar/21 ]

Closing as mappings are visible in definitions app.

Generated at Mon Feb 12 09:14:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.