You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Commas are accepted when adding an alias, however when being scraped via Stash (eg ScrapeSinglePerformer) they're not escaped or quoted etc in the return list of aliases, so it will then split an alias with a comma into 2 aliases. This becomes a problem for stash when the comma is what's keeping the aliases distinct.
To Reproduce
Steps to reproduce the behavior:
Add an alias with a comma when creating or modifying a performer
Expected behavior
Ideally these would be escaped and thus valid everywhere, but it may be simply easier for now to disallow commas in aliases or split them on a comma at the stash-box point of entry.
Describe the bug
Commas are accepted when adding an alias, however when being scraped via Stash (eg ScrapeSinglePerformer) they're not escaped or quoted etc in the return list of aliases, so it will then split an alias with a comma into 2 aliases. This becomes a problem for stash when the comma is what's keeping the aliases distinct.
To Reproduce
Steps to reproduce the behavior:
{ "data": { "scrapeSinglePerformer": [ { ... "aliases": "abc, abc, def", ... "__typename": "ScrapedPerformer" } ] } }
Expected behavior
Ideally these would be escaped and thus valid everywhere, but it may be simply easier for now to disallow commas in aliases or split them on a comma at the stash-box point of entry.
{ "data": { "scrapeSinglePerformer": [ { ... "aliases": ["abc,abc", "def"], ... "__typename": "ScrapedPerformer" } ] } }
The text was updated successfully, but these errors were encountered: