Don't have any objections to that, but I guess we need to specify which options we want, and document them on wiki too.

So I would like to implement something like:

#defaultView:Graph{arrows:'red', layout:'hierarchical', othterOption:'Foo'}

Which would allow you to pass options to default view.

In T155973#3366705, @Jonas wrote:

So I would like to implement something like:

#defaultView:Graph{arrows:'red', layout:'hierarchical', othterOption:'Foo'}

Which would allow you to pass options to default view.

One issue with that: How would it handle settings spanning multiple lines? "#" only comments out one line, and if settings get large/complicated enough to be unwieldy without line breaks, having the constraint could be a problem.

@Jonas just a slight change – I’d prefer standard JSON (not sure if you had something different in mind or the differences are only accidental):

#defaultView:Graph{"arrows":"red", "layout":"hierarchical", "otherOption":"Foo"}

@Yair_rand templates have the same problem (and worse, in my opinion – I think templates are generally longer than result view options), but I don’t think we should let that block us from adding this feature (we can improve both things at the same time later: they’re both query metadata).

@Lucas_Werkmeister_WMDE Seems reasonable. Syntax issues and inconsistency between query metadata types can be resolved later.

Change 385427 had a related patch set uploaded (by Jonas Kress (WMDE); owner: Jonas Kress (WMDE)):
[wikidata/query/gui@master] Allow passing options to Result Views

https://gerrit.wikimedia.org/r/385427

Change 385427 merged by jenkins-bot:
[wikidata/query/gui@master] Allow passing options to Result Views

https://gerrit.wikimedia.org/r/385427