-
Notifications
You must be signed in to change notification settings - Fork 307
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
Format client side component properties for SPFx commands in SharePoint #5975
Comments
The question is, if we should replace the output with just the properties, or should we add a new property named |
We have a few commands that do something similar. They have a flag that replaces the entire output. Example: spo sitescript get for example. So for the sake of consistency, my vote would go to replacing the entire output. |
Hmmm, good point. For consistency, shall we then use the full property name, ie. |
Ok, updated the spec. |
Great enhancement, specs look clear to me so let's open it up. |
We currently have a few commands in
spo
that do stuff with SPFx solutions (spo applicationcustomizer
,spo commandset
, ...). These are great commands to do stuff with your deployed SPFx solutions.For example: it's really easy to see which properties are set on the SPFx custom action. One annoying thing here is that the properties are string escaped, so the result looks like this:
It would improve the readability a lot if you could specify a flag so that only the client-side properties are printed as JSON:
So, I suggest that we add a new flag to a few SPO SPFx commands:
-p, --clientSideComponentProperties
Commands to update:
The text was updated successfully, but these errors were encountered: