fix: SyntaxWarning for Escape Characters in String Literals #4792
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Removes
SyntaxWarning: invalid escape sequence
messages during server start.As of 3.12, putting escape characters in string literals will cause this warning. This primarily effects regular expressions, requiring them to be raw strings instead of normal string literals. This pull requests fixes the warnings raised by the
punctuation
regular expression in theSearchFilter
class and the slug check within theupdate
function of theRepositoryCookbooks
class.Which issue(s) this PR fixes:
Fixes #4775
Special notes for your reviewer:
First PR -- Please let me know if I'm not meeting any of the contribution standards.
Testing
mealie-next
and my branch with the search string!@#$%^&*()_-+="'<>,.?/~
and verified that the translation onquery_search.py ln:25
had the same result.Couldn't figure how the branch of code for the
RepositoryCookbooks
change is executed so would appreciate any pointers.