For more inspiration:

• wikibase-edit already uses a JS/JSON representation of edits. It should be feature complete (supporting ranks, snaktypes, and all)
• QuickStatements format can be converted to the wikibase-edit format via the lib quickstatements-to-wikibase-edit
• There is also an ongoing experimentation to add a reconciliation syntax to the wikibase-edit format

this is likely to be due to the custom-config.json file not being properly fetched from the client: it works when building the image from the current master, instead of relying on wikibase/wdqs-frontend:latest image (it could be that it now also works on latest if it was updated lately)

could you tell more on that merge plugin? what is it (found it), where is it referenced and used?

reverting to wikibase/wikibase:1.32-bundle seems to solves the issue, so that would make the suspect change be somewhere between cd41afd and 9344529

I don't know if I am or not using the composer merge plugin, I'm using the wikibase/wikibase:1.33-bundle docker image without any additional extension

the composer.lock I found in /var/www/html/extensions/Wikibase

@Addshore it could apply to any image, not just wdqs-frontend:: when pulling wikibase/wikibase:1.33-bundle the name tells me it was built from the wikibase/1.33 folder, but that folder has been modified several times:

* 531fbda - (10 weeks ago) More cleanups for performance, use better names and passwords - Amir Sarabadani
* a294b27 - (10 weeks ago) Use a commit that works for 1.33 - Amir Sarabadani
* 7e8697d - (2 months ago) Explicitly download 1.34-wmf.8 of EntitySchema for 1.33 bundle - Amir Sarabadani
* 562e69b - (2 months ago) Add 1.33 + EntitySchema extension - Amir Sarabadani

How can I know at which commit it was built?

ping @nichtich

I wasn't aware of the Grid, looks like it was what I was looking for indeed :)
This task can thus be closed as far as I'm concerned.

@Lydia_Pintscher it seems to work now! I was able to create L4673

ooh I didn't see the preview button, but yes, just adding a href to query.wikidata.org#SELECT... URLs and not preventing default on click events when opened outside shouldn't be too hard(?) and of great value for tabs extensive users :)

yes, the examples dialog, but mostly the links to the example queries themselves: every layout that has the possibility to be built from the URL (so for example queries that would be https://query.wikidata.org/#[the serialized SPARQL]), should ideally offer the possibility to be open outside)

@MrSteff hey, feel free to reach me on IRC (user: maxlath) if/when you want to come, so that we don't miss each others

@MrSteff sure! simply come to the Blunzn room anytime, I'm there most of the time (usually first desk at your right when you enter)

@Framawiki I'm in the Blunzn room (1st level), come anytime!

Copying here the suggestion I made in the mailing list A plea for incremental dumps thread:

@JanZerebecki oh sorry, that should be published now

Hi!
Following today's issue with the query GUI, I had a look at the code and thought of some optimizations, without being aware of this discussion, leading to the writing of a simple building script.
Given I did it without this conversation in mind, feel free to ignore it or just take is as inspiration. If you want to use a more elaborate build process, particularly fast in development mode, I would recommend having a look at brunch which is specialized in building this kind of front app. See here how it relates to Grunt, Gulp and others

So it's time to eliminate the pretense that clients can manually construct the cookies instead of handing the standard HTTP cookie headers.

thanks @hoo for the quick answer, I opened a discussion here

ok, so I came to solve all my problems, including the very nasty

so that's the (coffeescript) code I'm using, with everything in the body, that created the noentity error

breq = require 'bluereq'
Promise = require 'bluebird'
_ = require './utils'

now, passing the parameters in the body, I get

I have been trying with both that good ol' /usr/bin/curl and a NodeJs lib called request (or a  promise-wrapped version of it)