-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Remove broken features from web interface #37
Conversation
We should probably do a hard fork from jellyfin-archive/jellyfin-apiclient-javascript@c390d77 and publish it to npm or whatever. Then import with <favorite package manager>. |
Looking good :) |
var infoHtml = responses[0]; | ||
var downloadsHtml = responses[1]; | ||
|
||
return new Promise(function (resolve, reject) { |
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.
Hmm, there's nothing to resolve these new promises unless I'm missing something.
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.
Yeah, turns out I had it right the first time. The promises were only made to call some external methods and they were resolved right here. Without the method calls the promises aren't necessary. I'll remove them in a minute.
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.
The way I see it there's two solutions. Removing the promises and not adding them to the promise array (this one you missed), or resolving them immediately. I prefer the former. Sorry I didn't suggest that instead...
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.
Isn't that what I did the first time though? I removed the promises and didn't return any values from those two methods.
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.
Check the current source for my original solution, I added it again.
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.
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.
How about my latest commit? Removed the return statement so it just loads normally.
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, remaining de-uglification should be done in a separate PR.
Co-Authored-By: dkanada <[email protected]>
Nice. LGTM now. |
Several components in the javascript API don't have any source code available, including wakeonlan, serverdiscovery, cameraroll, and fileupload, which I assume was supposed to be a part of the
cameraroll
feature. We might want to implementserverdiscovery
eventually, butwakeonlan
andcameraroll
should be removed. I would also like to remove all sync related functionality and simply extend the download feature for mobile as well. I will list some reasons for these actions below that I mentioned in chat, but they are all my personal opinions so everything is open to discussion. My primary reason for removing these features is to make the code easier to maintain without losing any functionality.This is also a good time to ask what we are doing to sync the jellyfin-apiclient-javascript between its own repository and this project. I don't want to make changes here and then have to manually edit the other repository in the future.