| Jan_Dittrich added a comment. |
we would have a Regex, but it carries no context what it would do?
Yup.
That sounds problematic to me, regexes are hard enough to read even with comments and context. For a hack one runs for oneself it is OK, but having it as a more central element in the infrastructure I think it will cause us problems.
Could we use capture groups and see which does (not) capture?
I don’t see how – all we get back from the query service is “matches” or “doesn’t match”, and doing anything not on the query service opens us up to DoS attacks via expensive regexes.
Is that a constraint-by-principle or something that the queray service could do but currently does not?
TASK DETAIL
EMAIL PREFERENCES
To: Jan_Dittrich
Cc: Lucas_Werkmeister_WMDE, Jan_Dittrich, Aklapper, Esc3300, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331
Cc: Lucas_Werkmeister_WMDE, Jan_Dittrich, Aklapper, Esc3300, GoranSMilovanovic, QZanden, Izno, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
