Seb35 added a comment.
For the first point, when there is SPARQL error, there is already an error displayed in JavaScript console saying where is located the error (line and character). The SPARQL analysis is provided by this library <https://github.com/RubenVerborgh/SPARQL.js>. To solve this first point, the error could be caught and displayed in the UI. Also, for a good UX, it should be thought when you display such error: when the user is typing? or when submitting the request? My point about the timing is: when the user is typing there are always errors because the SPARQL request is not finished. E.g. when I type: SELECT ?item { there is an error on line 2. So either the error should be displayed when the SPARQL request is submitted (but this is not really useful because Blazegraph already complains when there is an error), either there should be a timer to detect when the user stops typing (e.g. 2 seconds) but the user could stop typing to think about his/her request and be bothered by the error displayed. I’m not sure what is the best scenario. TASK DETAIL https://phabricator.wikimedia.org/T229393 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Seb35 Cc: Seb35, Lea_Lacroix_WMDE, Lydia_Pintscher, Smalyshev, VIGNERON, Aklapper, darthmon_wmde, DannyS712, Nandana, Lahi, Gq86, Lucas_Werkmeister_WMDE, GoranSMilovanovic, QZanden, EBjune, merbst, LawExplorer, Salgo60, B20180, _jensen, rosalieper, Jonas, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
