Query editor should not resort query by key

Although key order doesn't make any difference to the API, you can see in the docs that changing key order can make the query clearer. Unfortunately, the query editor automatically sorts the keys in alphabetical order on submission. In addition to making the query more confusing to a novice, it also is disconcerting to have things jump around.

Bug / Feature Request

Ticket Type:

Category:

top ↑

Similar topics in Freebase

  • Text Clipping

    Text Clipping

    This is fairly conspicuous: displayed field names for topics appear clipped in Firefox 2.0.0.1/Ubuntu.Attached screenshot.
  • Error generated when adding image from URL

  • Link dialog in description editor should be prefilled with selected text

    When editing a description, to add a link I highlight text and click the "link" icon.  Usually I end up having to immediately retype the text I just selected into the metaweb link field.  Seems like it might make sense to pre-fill that field with the selected text to save time (or even...
  • Usability of type selection dropdown list

    In some cases, the autocomplete entry can be frustrating to use.For instance, if "Web Site Category" has been selected as a type, and I want to correct it to "Web Site", then I cannot just delete the word "Category" and hit enter -- this just re-selects "Web Site Category".  I need to delete...
  • Query editor too tall

    The query editor is too tall to fit without scrolling even when maximized on my 1400x1050 screen using normal browser settings. It should at least fit on a 1280x1024 screen, and it would be great if the layout were flexible enough to accommodate a variety of window sizes.
  • Can't link to users in text editor, favorite topics

    I'd like to be able to link to users as internal Metaweb links. But at least when I try it for my two accounts ("/user/william" and "/user/querybuilder_bot") the autocomplete can't find them, both in the text editor link tool and in the "favorite topics" autocomplete.
  • Each property should have help text

    Although many properties are self-explanatory, others are mysterious to the casual editor. It would be great if each property's pulldown menu in the topic viewer had a way to get more information on what the property is and how best to use it. 
  • Viewing an invalid user gives blank page

    Viewing an invalid user gets a page that is blank except for a couple of images. For example:http://www.freebase.com/view/user?id=/user/sadfIt's not a big deal, as people shouldn't be hand-editing URLs, but it would be better if it there were some sort of "user not found" message.

These people have edited this topic:

Edit this topic
Edit and Show details

Add or delete facts, download data in JSON or RDF formats, and explore topic metadata.

Freebase Logo
What is Freebase?

Freebase is a huge collection of facts, built by people like you. Freebase connects facts in ways other sites can't, giving you new ways to explore millions of subjects.
You can help improve it!

Freebase Attribution

Freebase data is free for use under the CC-BY license.

Learn more about Freebase licensing and attribution