Skip to content

add artist/albumartist filter to media file #4001

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

Merged
merged 4 commits into from
Apr 25, 2025

Conversation

kgarner7
Copy link
Contributor

No description provided.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

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

Important

Looks good to me! 👍

Reviewed everything up to 3409b2e in 2 minutes and 10 seconds. Click for details.
  • Reviewed 12 lines of code in 1 files
  • Skipped 0 files when reviewing.
  • Skipped posting 2 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. persistence/mediafile_repository.go:95
  • Draft comment:
    Ensure that 'artistFilter' is implemented consistently and handles cases similar to other string filters. Consider adding unit tests for this new filter.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% The comment violates several rules: 1) It starts with "Ensure that..." which is explicitly discouraged 2) It's speculative without evidence of actual issues 3) It suggests adding tests which is not directly related to the code change 4) Without seeing the artistFilter implementation, we can't verify if there are actual consistency issues. Maybe there are actual inconsistencies in the artistFilter implementation that would make this comment valuable. The suggestion for tests could prevent future issues. Without seeing the artistFilter implementation, we can't verify any inconsistencies. The comment is speculative and uses "ensure that" phrasing which violates our rules. Delete this comment as it is speculative, uses discouraged phrasing, and makes suggestions without evidence of actual issues.
2. persistence/mediafile_repository.go:95
  • Draft comment:
    The PR title mentions adding both artist and albumartist filters, but only the 'artist' filter is added. Confirm if an albumartist filter is also needed or if the artistFilter covers both cases.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to confirm if an additional filter is needed based on the PR title. This is not a specific code suggestion or a request for a test, and it violates the rule against asking the author to confirm their intention.

Workflow ID: wflow_gbK7YV4QvqcQqBRH

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@deluan deluan merged commit 3d6a238 into navidrome:master Apr 25, 2025
31 checks passed
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