-
Notifications
You must be signed in to change notification settings - Fork 492
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
fix: add folder #924
fix: add folder #924
Conversation
@@ -241,17 +241,22 @@ export default (opts = {}) => { | |||
progress: updateProgress | |||
}) | |||
|
|||
if (res.length !== streams.length + 1) { | |||
if (res.length !== streams.length + 2) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure when this changed, but it was always failing because of this!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting, it's returning an entry for the folder, and the parent of the folder. This fixes our logic around it, so +1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -241,17 +241,22 @@ export default (opts = {}) => { | |||
progress: updateProgress | |||
}) | |||
|
|||
if (res.length !== streams.length + 1) { | |||
if (res.length !== streams.length + 2) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
interesting, it's returning an entry for the folder, and the parent of the folder. This fixes our logic around it, so +1
Adding a folder was failing because of the length of the api response. It would also fail and give an incoherent error if adding a folder with an existing folder name.
Fixes #922.