You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Yes. The current pac commands that include --publisher-name are looking for the publisher name without spaces. This is a problem as it's very common for a publisher display name to have spaces.
Describe the solution you'd like
Investigation into the existing pac command line to understand if using single quotes, double quotes, or some other special character would allow support for publisher names with spaces. Alternatively, if this plugin could support it via a custom pac command that does support this.
Describe alternatives you've considered
The current solution is to create a dummy solution with a publisher name without spaces to get the PCF control into the environment and then move it the correct solution with the correct publisher.
Additional context
This is an issue with the pac commands as far as I can tell, so this is a request to see if this tool could work around the limitation.
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label enhancement to this issue, with a confidence of 0.89. Please mark this comment with 👍 or 👎 to give our bot feedback!
Is your feature request related to a problem? Please describe.
Yes. The current
pac
commands that include--publisher-name
are looking for the publisher name without spaces. This is a problem as it's very common for a publisher display name to have spaces.Describe the solution you'd like
Investigation into the existing
pac
command line to understand if using single quotes, double quotes, or some other special character would allow support for publisher names with spaces. Alternatively, if this plugin could support it via a custom pac command that does support this.Describe alternatives you've considered
The current solution is to create a dummy solution with a publisher name without spaces to get the PCF control into the environment and then move it the correct solution with the correct publisher.
Additional context
This is an issue with the
pac
commands as far as I can tell, so this is a request to see if this tool could work around the limitation.The text was updated successfully, but these errors were encountered: