-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Mappings for _api/navigation/menuState
#1257
Labels
area: model 📐
Related to the core SDK models
Comments
@JakeStanger : that would make sense as a change. Is this something you could take on? |
Possibly, but it wouldn't be short-term nor something I could commit to I'm afraid. I will likely need a solution to this for a work project in a few weeks, so time constraints will control whether I can add something in here or not. I'll do my best to keep you updated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Category
Describe the feature
There are some SP navigation settings that can only be set via the
_api/navigation/menuState
and_api/navigation/saveMenuState
REST API. Currently these are not nicely exposed via PnP Core.Describe the solution you'd like
As a minimum, It should be possible to get and save the menu state directly, using built-in PnP Core methods.
Ideally, some of the options should also be exposed via the regular navigation, with PnP Core automatically switching endpoint accordingly. For example, the "open in a new tab" option should be settable on
NavigationNodeOptions
, and then the library will usesaveMenuState
instead of the 'regular' web navigation endpoint.Additional context
PnP PowerShell implementation for
Add-PnPNavigationNode
cmdlet, which aligns with the above:https://github.com/pnp/powershell/blob/ccee58d064da543e40a4a7a872ad9574f8a108ed/src/Commands/Navigation/AddNavigationNode.cs#L125
The text was updated successfully, but these errors were encountered: