These changes follow guidance from Sandi and from the general DOM specification that the `tabindex` attribute (along with Angular's `isFocusable` and `isTabbable` attributes) should only be included on elements that can be interacted with via mouse clicks or keyboard input.

A number of elements in the degree planner view were non-interactive by design but still were in tabbable. This commit removes tabbing from those non-interactive elements.

Isaac Evavold authored 5 years ago and Isaac Evavold committed 5 years ago

Previously, the alert component only worked with the degree planner view. Now the alert component can be used in any view that supplies a list of alerts.

Error caused when user loaded the degree planner (thus initializing the termcode factory), switched to the dars view (which doesn't reset the termcode factory), then switched back to the degree planner (which attempted to initialize an already initialized termcode factory).

This fixes the bug by only attempting to initialize the termcode factory if the termcode factory is uninitialized

Isaac Evavold authored 5 years ago and Isaac Evavold committed 5 years ago

Bug was caused because the course details modal didn't open until the course details API call had resolved. If the user double clicked on the course item, two clicks were registered before the first modal had opened which trigged a second modal to open. Now the course details modal always opens immediately (thus preventing subsequent clicks from targeting the course item element) and the details modal is open while it waits for the details API to resolve.

- Creates DARS view as a child view of the degree planner
- Moves constants resolver services into the degree planner router instead of the app router
- Updates the navigation links so that the degree planner link and the dars link will be appropriately marked as "active"