pnp/cli-microsoft365

[Enhancement] - Add more options to `spo tenant settings set`

Open

#5,034 opened on Jun 9, 2023

View on GitHub
 (19 comments) (0 reactions) (0 assignees)TypeScript (399 forks)auto 404
enhancementhelp wantedkeep-openneeds research

Repository metrics

Stars
 (1,390 stars)
PR merge metrics
 (PR metrics pending)

Description

Currently we cannot enable/disable the link Return to classic SharePoint on modern SharePoint list and library pages at tenant level using CLI for Microsoft 365.

Can we enhance spo tenant settings set cmdlet to support additional parameter (say --DisableBackToClassic [DisableBackToClassic]) which will allow users to enable/disable the link Return to classic SharePoint on modern SharePoint list and library pages?

I would like to contribute to this library for above enhancement request. Thank you!

Contributor guide

Research direction
Review the existing implementation of the `spo tenant settings set` command in the CLI for Microsoft 365 repository. Identify the current parameters and the corresponding SharePoint REST API calls. Add a new optional parameter ` DisableBackToClassic` to the command, update the command's JSON schema, and implement the logic to call the appropriate API to enable or disable the 'Return to classic SharePoint' link at the tenant level. Ensure proper error handling and update the help documentation.
Tech stack
typescript
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptCLI for Microsoft 365SharePoint REST API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65