Are there some controls that are outdated in this library and still explained in the demo site? #4257
-
|
I was seeing the demo site and when i started to learn about the nav menus i saw a message up that says "IMPORTANT If you DO NOT want to upgrade to these new menu components, you can continue to use the pre-version 3.2 components. The only thing you need to do is to change the name of the FluentNavMenu component in your application to FluentNavMenuTree. Everything works exactly as before by changing the name of this FluentNavMenu component in your application. (This probably needs to be done in one place only). The FluentNavMenuGroup and FluentNavMenuLink components have not been changed and do not need to be altered. We consider the FluentNavMenuTree, FluentNavMenuGroup and FluentNavMenuLink components as deprecated and will remove them in a future version. If you wish to upgrade to the new menu components, please refer to the Upgrade guide for more information.". So i am kind of confused, are all the controls that are listed in the demo site are up to date? you guys mentioned the FluentNavMenuTree, FluentNavMenuGroup and FluentNavMenuLink to be old controls but there is a whole tab "NavMenuTree" that talks about them still, so should i learn them or it should be enough with "NavMenu" tab in the demo? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
We consider the FluentNavMenuTree, FluentNavMenuGroup and FluentNavMenuLink components as deprecated and will remove them in a future version. Does that not say enough? These 3 are deprecated. But they were there already, can be in use by developers so we can't just remove them whenever we like. They will not be there anymore in v5. Bring deprecated means they will not be receiving any updates anymore. |
Beta Was this translation helpful? Give feedback.
We consider the FluentNavMenuTree, FluentNavMenuGroup and FluentNavMenuLink components as deprecated and will remove them in a future version.
Does that not say enough?
These 3 are deprecated. But they were there already, can be in use by developers so we can't just remove them whenever we like. They will not be there anymore in v5.
Bring deprecated means they will not be receiving any updates anymore.