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

Resolve linting issues #1

Merged
merged 7 commits into from
Jul 8, 2024
Merged

Resolve linting issues #1

merged 7 commits into from
Jul 8, 2024

Conversation

neBM
Copy link

@neBM neBM commented Jun 30, 2024

I've had a look at some ideas for solving the detekt issues and I believe we can abstract out a large proportion of the params from the JellyfinMediaSource.

For convenience, I've broken the PR into two commits:

  • One commit resolves the trivial quick fixes
  • Another solves LongParameterList error

Please feel free to merge if you like what you see. 😄

This is in relation to jellyfin#1404.

@neBM
Copy link
Author

neBM commented Jun 30, 2024

I haven't been able to test this as I'm having issues spawning an emulator so I've marked this as draft, but I'm hoping it's a good start to a solution.

@7ritn
Copy link
Owner

7ritn commented Jul 1, 2024

I really like this idea of splitting between a local and a remote jellyfin data source. However, I wonder if it could be confusing, since the RemoteJellyfinMediaSource could also potentially use a cached download if available.

I will look into your changes and test them out. Thanks so much!

Copy link
Owner

@7ritn 7ritn left a comment

Choose a reason for hiding this comment

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

I think it is a really good idea, however oftentimes I think a JellyfinMediaSource would be more approriate compare to the specific RemoteJellyfinMediaSource. What do you think? Furthermore moving the additional downloads specs into the LocalJellyfinMediaSource structure could be really beneficial

@neBM
Copy link
Author

neBM commented Jul 1, 2024

I think it is a really good idea, however oftentimes I think a JellyfinMediaSource would be more approriate compare to the specific RemoteJellyfinMediaSource. What do you think? Furthermore moving the additional downloads specs into the LocalJellyfinMediaSource structure could be really beneficial

Ah! I hadn't considered caching... good thinking — I agree. Do you have any preference over what we could call the POJO?

Ooo yes, I'll have a look into migrating the additional downloads specs adapter too 😋

@neBM neBM marked this pull request as ready for review July 2, 2024 21:39
@neBM
Copy link
Author

neBM commented Jul 2, 2024

Marking this as ready as I've done quick testing locally and current functionality appears to be working. I'll continue with the suggested changes.

Copy link
Owner

@7ritn 7ritn left a comment

Choose a reason for hiding this comment

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

Looks really good, it is basically ready to merge, just wondering regarding the enforcement of RemoteJellyfinMediaSource when switching Audio or Subtitle Track?

@7ritn
Copy link
Owner

7ritn commented Jul 3, 2024

So you want to work on moving the downloads specs from the database to the LocalJellyfinMediaSource structure?

@neBM neBM requested a review from 7ritn July 6, 2024 23:13
@neBM
Copy link
Author

neBM commented Jul 6, 2024

So you want to work on moving the downloads specs from the database to the LocalJellyfinMediaSource structure?

Hi! Yep, all done! Please have a look over the additions for me and let me know what you think.

It might be worth double checking switching with encoded subtitles as I don't have media to test this to hand.
This is in reference to:

return viewModel.queueManager.selectSubtitleStreamAndRestartPlayback(selectedMediaStream)

Copy link
Owner

@7ritn 7ritn left a comment

Choose a reason for hiding this comment

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

Looks good works well with external subtitles on my phone :)

@7ritn 7ritn merged commit 051de01 into 7ritn:download Jul 8, 2024
@7ritn
Copy link
Owner

7ritn commented Jul 8, 2024

Thanks for your work ^^

@neBM
Copy link
Author

neBM commented Jul 8, 2024

Thanks for your work ^^

And thank you for all your feedback :) That was good fun!

@neBM neBM deleted the download branch July 8, 2024 08:31
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.

2 participants