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
If you pass an option for --outputdirectory="'c:\somepath'" it will fail with “The given path's format is not supported.” This is because the option isn't removing the surrounding quotes like other options do. Ensure that all options that set values are doing so.
The text was updated successfully, but these errors were encountered:
ferventcoder
changed the title
Ensure outputdirectory options and all options can accept approved quoting format - “The given path's format is not supported.”
Setting outputdirectory with proper quoting can result in “The given path's format is not supported.”
Mar 10, 2018
ferventcoder
changed the title
Setting outputdirectory with proper quoting can result in “The given path's format is not supported.”
Setting output directory with proper quoting can result in “The given path's format is not supported.”
Mar 23, 2018
When setting output directory, if you do it in the proper manner as
suggested by the documentation, it will return an error with "The given
path's format is not supported." This is because the option is not
removing the surrounding quotes like the other options do.
Allow passing `--outputdirectory="'c:\somepath'"` in the proper manner
so that it matches consistency with all of the other options.
* stable:
(doc) Get-PackageParameters - fix example
(GH-1476) Ensure docs are for Get-PackageParameters
(doc) update generated docs
(doc) update release notes for 0.10.9
(GH-1517) Fix: Given path's format is not supported
(doc)(maint) CHANGELOG formatting
(doc) update licensed CHANGELOG
If you pass an option for
--outputdirectory="'c:\somepath'"
it will fail with “The given path's format is not supported.” This is because the option isn't removing the surrounding quotes like other options do. Ensure that all options that set values are doing so.The text was updated successfully, but these errors were encountered: