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

Hide entries whose scanlators are excluded from updates tab #1001

Open
4 tasks done
Secozzi opened this issue Jul 10, 2024 · 1 comment · May be fixed by #1623
Open
4 tasks done

Hide entries whose scanlators are excluded from updates tab #1001

Secozzi opened this issue Jul 10, 2024 · 1 comment · May be fixed by #1623
Labels
Feature request New feature or request
Milestone

Comments

@Secozzi
Copy link
Contributor

Secozzi commented Jul 10, 2024

Describe your suggested feature

As the title says, if I have a manga where I've excluded some scanlators and if new chapter with those scanlators appears, then they should not pop up in the updates tab, since I don't care about those scanlators.

Other details

Trying to click on an entry whose scanlator is excluded in filters from the updates tab will result in "Requested chapter of id ... not found in chapter list"

Acknowledgements

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
  • I have written a short but informative title.
  • I have updated the app to version 0.16.5.
  • I will fill out all of the requested information in this form.
@Secozzi Secozzi added the Feature request New feature or request label Jul 10, 2024
@AntsyLich AntsyLich added this to the v0.17.0 milestone Jul 11, 2024
@AntsyLich
Copy link
Member

Could potentially make it a filter and rework opening the filtered chapters

@AntsyLich AntsyLich modified the milestones: v0.17.0, v0.18.0 Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants