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
🐞 Describe the bug
As described in the docs, there are two ways to specify a space for spaces-cli to use when downloading a file. One is to use the -s command line option, and the other is to include it in the full download file url. The first path currently breaks with the error message 'Cannot read properties of null (reading 'includes')' . As far as I can tell this is coming from this line. Specifying a relative path instead of a full url causes the hostname to be undefined, which ends up blowing things up. The docs themselves provide a download example that uses a relative path, so I was expecting that to be supported.
📚 To Reproduce
try downloading just using a relative path
💡 Expected behavior
I should be able to use a relative path
🖼️ Screenshots
If applicable, add screenshots to help explain your problem.
⚙️ Environment
Version: 1.0.41
OS: fedora
Shell bash
The text was updated successfully, but these errors were encountered:
🐞 Describe the bug
As described in the docs, there are two ways to specify a space for spaces-cli to use when downloading a file. One is to use the -s command line option, and the other is to include it in the full download file url. The first path currently breaks with the error message 'Cannot read properties of null (reading 'includes')' . As far as I can tell this is coming from this line. Specifying a relative path instead of a full url causes the hostname to be undefined, which ends up blowing things up. The docs themselves provide a download example that uses a relative path, so I was expecting that to be supported.
📚 To Reproduce
try downloading just using a relative path
💡 Expected behavior
I should be able to use a relative path
🖼️ Screenshots
If applicable, add screenshots to help explain your problem.
⚙️ Environment
The text was updated successfully, but these errors were encountered: