Closed vnbaaij closed 7 months ago
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Some questions.
Why the Item 5 seems accessible, but the property Disabled=true
?
By default, I don't think that the Gap
between a NavLink
and a NavGroup
must be different.
Probably interesting to add an maximum width and ellipsis when the text is too long.
Some questions.
- Why the Item 5 seems accessible, but the property
Disabled=true
?
Small CSS issue. Was only checking for a.disabled
instead of just .disabled
- By default, I don't think that the
Gap
between aNavLink
and aNavGroup
must be different. Agreed. Setting it to empty string as default
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
Azure Static Web Apps: Your stage site is ready! Visit it here: https://black-pebble-0dc79cb03-819.westeurope.3.azurestaticapps.net
The existing NavMenu components utilized the TreeView components for displaying the hierarchical structure and was not using the native NavLink capabilities to render links. This meant we need to do link/url/route checking ourselves which did not work quite right.
This PR introduces new
FluentNavMenu
,FluentNavGroup
andFluentNavLinks
components which are based on the nativeNavLink
component.The original
FluentNavMenu
component had been renamed toFluentNavMenuTree
. TheFluentNavMenuGroup
andFluentNavMenuLink
have remained unchanged. To keep using the original implementation, the only change that needs to be done is to do this rename action in your code. These 3 components are now marked obsolete and will be removed in a future version.To upgrade to the new behavior, instructions have been added to the
Upgrade guide
Documentation and examples have been updated.