You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GHG Center wants to make some customizations to the nav bar in their instance. Long term, we know that we want a nav component that can be customized on the instance side, making it easier to maintain and iterate on our core VEDA component. So, it makes sense to allow for the GHG R3 customizations to occur on the instance side. We need to enable that
Acceptance Criteria
Any customizations to the nav bar (titles, layout, color, logos, dropdowns, etc) occur on the instance side of the VEDA Dashboard implementation
The text was updated successfully, but these errors were encountered:
**Related Ticket:** #1071
### Description of Changes
Exporting nav from UI side so it can be used to override its menu from
GHG side.
The code changes look like a lot, but most of them are just pieces
moving around and making the components accept props.
This change checks the veda.config to see if there are any defined
`navItems` and use it if there is one instead of the default one. There
can be 4 types of nav item, which are `internalLink`, `externalLink`,
`dropdown`, `modal`. The details of each type will be documented.
### Notes & Questions About Changes
The current version does not mark the dropdown item as 'active' when its
child is selected.
### Validation / Testing
_{Update with info on what can be manually validated in the Deploy
Preview link for example "Validate style updates to selection modal do
NOT affect cards"}_
Instance pr: US-GHG-Center/veda-config-ghg#457
- [x] remove test config from veda.config
- [ ] Add documentation : will do it after style polish
Context
GHG Center wants to make some customizations to the nav bar in their instance. Long term, we know that we want a nav component that can be customized on the instance side, making it easier to maintain and iterate on our core VEDA component. So, it makes sense to allow for the GHG R3 customizations to occur on the instance side. We need to enable that
Acceptance Criteria
The text was updated successfully, but these errors were encountered: