At the moment the spo customaciton get prints the following:
spo customaction get -i 7b115268-c431-458b-9eac-0b22419a1486 -u https://xxx.sharepoint.com/sites/xx -s Web
Name : customaction2
Id : 7b115268-c431-458b-9eac-0b22419a1486
Location : Microsoft.SharePoint.StandardMenu
Scope : Web
ClientSideComponentId : 00000000-0000-0000-0000-000000000000
ClientSideComponentProperties: ""
Would it be a good idea to have additional -d, --details [details] option? It can print the full output from the REST call i.e.
export interface CustomAction {
"odata.null": boolean;
ClientSideComponentId: string;
ClientSideComponentProperties: Object;
CommandUIExtension: Object;
Description: string;
Group: string;
Id: string;
ImageUrl: string;
Location: string;
Name: string;
RegistrationId: number;
RegistrationType: number;
Rights: {
High: number,
Low: number
};
Scope: number;
ScriptBlock: string;
ScriptSrc: string;
Sequence: number;
Title: string;
Url: string;
VersionOfUserCustomAction: string;
}Additional action is to check if those properties are valid for all the User Custom Action Locations
Would it worth implementing that at this early stage? or the focus should be to bring other commands?
That issue can be closed if now is not the time for it. We can always rise it later again.
At the moment the
spo customaciton getprints the following:Would it be a good idea to have additional
-d, --details [details]option? It can print the full output from the REST call i.e.Additional action is to check if those properties are valid for all the User Custom Action
LocationsWould it worth implementing that at this early stage? or the focus should be to bring other commands?
That issue can be closed if now is not the time for it. We can always rise it later again.