Add "require" option and beta image publish workflow #15
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.
Issue: #14
Currently, when comparing two values, we use the
.includes()
function. For example:[1,2,3,4,5].includes(3)
will returntrue
because the number3
appears in the array"The quick brown fox jumps over the lazy dog".includes("fox")
will returntrue
because the wordfox
is present in the stringThis is safer than using
x === y
and works 99% of the time.The user who reported the issue says they have a condition for the keyword
anime
. They want anything with that keyword to trigger a specific filter. They came across a movie containing the keywordbased on anime
which incorrectly triggered their condition, because we use the.include()
function. So what happened was:"based on anime".includes("anime")
->true
To help with this I added a new
require
option which will only returntrue
if the values match exactly.Also, this change will first be released in the new
beta
image to allow the user to test it before we make a public release. This is because we don't want to accidentally brick people's existing implementations.Ignore the spacing changes they're just automatic formatting from an extension.