Skip to content
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 premiere stuff and fix crashes caused by earlier removals #8

Merged
merged 11 commits into from
Jan 16, 2019

Conversation

cvium
Copy link
Member

@cvium cvium commented Jan 10, 2019

This is the frontend part of jellyfin/jellyfin#412

Fixes jellyfin/jellyfin#122

@cvium
Copy link
Member Author

cvium commented Jan 10, 2019

cc @JustAMan

@dkanada
Copy link
Member

dkanada commented Jan 11, 2019

The last change here inadvertently broke the android client so I will be checking up again after this one to see what happens. Turns out there was some weird stuff going on in connectlogin.js to initialize the ApiClient for android devices, no clue why the web frontend didn't see any issues.

JustAMan
JustAMan previously approved these changes Jan 11, 2019
@JustAMan JustAMan dismissed their stale review January 11, 2019 13:02

forgot to read all the changes

@JustAMan JustAMan changed the base branch from master to dev January 11, 2019 13:56
@cvium
Copy link
Member Author

cvium commented Jan 11, 2019

@JustAMan I haven't really bothered cleaning up the plugincatalogpage since I don't know if we're gonna keep it.

Regarding the livetv indexes, I dunno. It seems it's throughout the dashboard ui that data-index is used to identify stuff.

Copy link
Contributor

@JustAMan JustAMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good if you can address my remaining comments from previous review, too.
I'm going to drop questions on indices for now.

@cvium
Copy link
Member Author

cvium commented Jan 12, 2019

Would be good if you can address my remaining comments from previous review, too.

@JustAMan which ones? I couldn't find any. Maybe because I already force pushed?

Copy link
Contributor

@JustAMan JustAMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've copied my yet un-addressed comments to this separate review, closing them in previous one.

if (session.TranscodingInfo && session.TranscodingInfo.TranscodeReasons && session.TranscodingInfo.TranscodeReasons.length) {
text.push("<br/>");
text.push(globalize.translate("sharedcomponents#LabelReasonForTranscoding"));
showTranscodeReasons = true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not just insert the forEach loop from below here instead of a flag?..

}

if (showTranscodeReasons) {
session.TranscodingInfo.TranscodeReasons.forEach(function (t__e) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

t__e seems a remaining stuff from de-ulglification

}

function populateList(options) {
populateListInternal(options)
populateListInternal(options);
}

function getHeaderText(category) {
category.replace(" ", "").replace(" ", "");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wtf does this double replace mean, isn't one enough?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a no-op essentially. String.replace() returns a new string 🤷‍♂️

@cvium
Copy link
Member Author

cvium commented Jan 14, 2019

@JustAMan Done

Copy link
Contributor

@JustAMan JustAMan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing stuff!

@joshuaboniface joshuaboniface changed the title Remove premiere stuff (and fix crashes caused by earlier removals) Remove premiere stuff and fix crashes caused by earlier removals Jan 16, 2019
@joshuaboniface joshuaboniface merged commit a2c008a into jellyfin:dev Jan 16, 2019
@cvium cvium deleted the remove_premiere_fix_crashes branch January 16, 2019 18:50
@joshuaboniface joshuaboniface mentioned this pull request Jan 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants