@Shpigford mentioned in a previous issue that pltlst supports pipe-separated values.
After some experimentation, I've found this only works (using artists) with the contains modifier option (not is). Which works fine for most values but not all. E.g. Having a value of Sia results in lots of false hits, such as Staasia Daniels and Artemisia. Similarly Air and even Lorde have lots of false hits (which "breaks" the playlist effectively). Note, adding spaces around the term does not work (| Air |).
One possible fix for this is to support the pipe syntax with the is modifier (currently it returns zero results for even simple pipe queries), assuming it's possible via the Spotify API.
Alternatively some sort of additional syntax could also overcome it (word boundaries or startswith or endswith chars - ^ & $), etc.
@Shpigford mentioned in a previous issue that
pltlstsupports pipe-separated values.After some experimentation, I've found this only works (using artists) with the
containsmodifier option (notis). Which works fine for most values but not all. E.g. Having a value ofSiaresults in lots of false hits, such asStaasia DanielsandArtemisia. SimilarlyAirand evenLordehave lots of false hits (which "breaks" the playlist effectively). Note, adding spaces around the term does not work (| Air |).One possible fix for this is to support the pipe syntax with the
ismodifier (currently it returns zero results for even simple pipe queries), assuming it's possible via the Spotify API.Alternatively some sort of additional syntax could also overcome it (word boundaries or startswith or endswith chars -
^&$), etc.