-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix the no_convert option of the convert plugin stopping conversion when there is only a partial match. #5376
Fix the no_convert option of the convert plugin stopping conversion when there is only a partial match. #5376
Conversation
I'm looking at the documentation for
I understand that the comma should work as a logical OR operator. @sanpoChew, can you confirm that Also, this may break users' configurations, please add some information in the changelog so that users know how to adjust. |
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.
Thanks for the PR, and for catching this bug! This seems like a good fix.
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.
Actually, just one request. Can you add a test that confirms that the comma OR functionality still works as expected with this change? Just as a test-coverage thing.
After that, if @bal-e is fine, this can be merged.
That is correct yes, if users want to maintain the existing behaviour they would need to add a comma. I have updated the changelog entry so that it is more helpful 👍 |
That makes sense, have added that test 👍 |
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.
Sorry for the delay, @sanpoChew. LGTM!
7b02690
to
4685a0b
Compare
There seems to be some failures unrelated to my code in the lint checks |
Seems like this was caused by GitHub failing DNS resolution internally. Have re-ran the workflows and it worked fine now. |
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.
Suggested something which should simplify testing
c761088
to
2e6e180
Compare
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.
Amazing stuff, looks super clean now! Thanks for catching this.
fantastic! thanks a lot for the guidance all 👍 |
Description
I was running the
convert
plugin with the following config:but anything that was 24/48 was also not being converted, this was due to the code returning
False
forshould_transcode
if any part of the query matches, rather than considering the whole query. This meant thatbitdepth:...16
was being ignored.I have changed this so the
no_convert
value is considered as one query.To Do
Documentation.