As it stands, the admin page for z3950_source can build a filtered link to the z3550_attr page. However, the links only allow you to open the destination page when opening the link in a new tab. This is the result of the admin page / basic admin page components not being built to handle route changes within an instance of the component. (They are not watching for route changes and re-initing themselves).
Options I'm exploring, each with little unexpected complexities:
Teach the components to watch for route changes.
Change the route reuse strategy for the admin pages to force non-reuse of components
Use a regular 'href' instead of a 'routerLink' for navigating between pages.
I have made progress building atop Jeff's config_field branch. Work in progress:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ berick/ lp1847800- secondary- admin-pages
As it stands, the admin page for z3950_source can build a filtered link to the z3550_attr page. However, the links only allow you to open the destination page when opening the link in a new tab. This is the result of the admin page / basic admin page components not being built to handle route changes within an instance of the component. (They are not watching for route changes and re-initing themselves).
Options I'm exploring, each with little unexpected complexities:
Teach the components to watch for route changes.
Change the route reuse strategy for the admin pages to force non-reuse of components
Use a regular 'href' instead of a 'routerLink' for navigating between pages.
More later