Consolidate spo site set and spo site classic set commands. Closes #1495#3450
Consolidate spo site set and spo site classic set commands. Closes #1495#3450martinlingstuyl wants to merge 1 commit intopnp:mainfrom
Conversation
cec6983 to
5144822
Compare
|
thanks @martinlingstuyl for your awesome work. Will review it shortly 😋 |
Adam-it
left a comment
There was a problem hiding this comment.
@martinlingstuyl thanks for this awesome contribution 👍you rock 🤩🤩
I tested it locally, changed a couple of site properties, lock state, applied a site design.. works really good 💪
I noticed a couple of details we might correct along the way. Please do consider them 🙏
Let me know if you will need any help 👍
e6a8762 to
450e068
Compare
|
good review @Adam-it 🤙 |
450e068 to
78d3caf
Compare
|
@martinlingstuyl thanks for considering my comments and adding the improvements 👍 you rock 🤩. do you think it's possible for you to also have a check on this one as well 🙏? I will mark the PR as draft for now until we fix up the tests 😉. Let me know if you would need any help I would love to do so 👍 |
78d3caf to
8c9d321
Compare
|
I apparently broke the tests with my last fix. Missed two |
|
you rock 🤩merged manually 👍 |
Closes #1495
Consolidates
spo site setandspo site classic setcommands.Remarks
Because of fallback issues, The code files and docs of
spo site classic sethave not been removed. It has not been added as an alias tospo site setand it can still be used. All the functionality has been copied over tospo site setthough. And a deprecation notice has been added to the docs.In the next major release, we can remove the code files for
spo site classic set.Also: I've refactored the code so that: a) less calls to SharePoint are executed and b) several options are now executed against all sites, group connected or not. For example:
noScriptSiteandlockState, these where only used insite classic set.