Skip to content
This repository was archived by the owner on Dec 20, 2018. It is now read-only.

ActivePage declarations missing on scaffolded Identity UI #1866

Closed
tstivers1990 opened this issue Jul 9, 2018 · 3 comments
Closed

ActivePage declarations missing on scaffolded Identity UI #1866

tstivers1990 opened this issue Jul 9, 2018 · 3 comments
Assignees
Labels
3 - Done bug patch-proposed PRI: 1 - Required Must be handled in a reasonable time SHP: Approved Shiproom has approved the issue
Milestone

Comments

@tstivers1990
Copy link
Contributor

tstivers1990 commented Jul 9, 2018

Some of the ActivePage declarations are missing on the default scaffolded Identity UI. This causes some pages not to show an active item in the relevant nav section.

Some pages also use an ActivePage declaration that doesn't have a corresponding item in the navigation section, resulting in those pages not showing an active navigation item.

I've created a pull request that adds the missing ActivePage declarations, and changes the ones that don't have a corresponding nav element to use an ActivePage declaration with the most relevant nav element. For example, the DeletePersonalData page was using ViewData["ActivePage"] = ManageNavPages.DeletePersonalData; There is no nav element for Delete Personal Data. I've changed it to use ViewData["ActivePage"] = ManageNavPages.PersonalData; instead, as there is a nav element for Personal Data, and that is the most relevant nav element for the page.

Any methods and variables within ManageNavPages that are no longer used after this changed were removed. For example, the ManageNavPages.DeletePersonalData variable is no longer used after the change, and neither is the ManageNavPages.DeletePeronalDataNavClass method. Therefore, both of them are removed.

I've also made the PageNavClass method private, as it is never accessed outside of its class and, based on the class' design, should only be referenced by public methods in the class, and not directly outside of the class.

PR: #1838

@javiercn
Copy link
Member

javiercn commented Jul 9, 2018

@tstivers1990 Thanks for filing the issue. It's clearer to me now. I've commented on the PR #1838. The changes look good, but we need to remove the breaking changes as we want to take this into a patch.

@mkArtakMSFT This is a patch candidate.

@mkArtakMSFT mkArtakMSFT added the SHP: Approval pending Shiproom approval is required for the issue label Jul 9, 2018
@mkArtakMSFT mkArtakMSFT added this to the 2.1.3 milestone Jul 9, 2018
@mkArtakMSFT mkArtakMSFT added bug 1 - Ready PRI: 1 - Required Must be handled in a reasonable time labels Jul 9, 2018
@mkArtakMSFT
Copy link
Member

Hey @vijayrkn, this will require also a fix in Scaffolder. I'll take this one to the Shiproom.

@vijayrkn
Copy link

vijayrkn commented Jul 9, 2018

@seancpeters - Can you please make the corresponding scaffolding change?

@mkArtakMSFT mkArtakMSFT added SHP: Approved Shiproom has approved the issue and removed SHP: Approval pending Shiproom approval is required for the issue labels Jul 10, 2018
javiercn pushed a commit that referenced this issue Jul 10, 2018
* Fix missing activepage declarations
* Change activepage declarations to correct values
* Add missing ActivePage
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
3 - Done bug patch-proposed PRI: 1 - Required Must be handled in a reasonable time SHP: Approved Shiproom has approved the issue
Projects
None yet
Development

No branches or pull requests

4 participants