New enhancements to the YQL console and editor

Filed under changelog, feature

Some new enhancements were recently made to the YQL console and editor.

Console:

  • New debug checkbox.
    • Checking this will simply add debug=true to your console URL. When debug=true is set, it enables open table debugging and viewing of YQL network calls.
  • New expand checkbox.
    • Checking this will expand the results section to full height.
  • Renamed “My Tables” to “My YQL”.
    • With this release, you have the ability to create YQL tables, environments and js files via the editor. The My YQL section lists those files based on those types. This is the section where you can launch the editor to edit the files and the area where you can delete your files.

      Some actions when clicking on the file names:

      • Clicking on a table name will put the store execute key into the yql statement area and desc the table.
      • Clicking on an environment name will load that environment by adding env=store://(your store execute key here) to the console.
      • JS files are only editable via the YQL editor.

      Only you will know what YQL files you have created, since you need to be logged in to create and view them. But you can share your YQL file store execute keys, as they can be run by anyone after sharing. Only share them if you want others to run that file.

Editor:

  • The ability to create different YQL file types.
    • You now can create Tables, YQL environments and JS files. Simply select the “Save as” drop down to save the type of file needed.
    • Regarding JS files, these are files you can y.include() into your execute statement in a table.
  • Dragging a YQL file from the sidebar onto the editor will produce a contextual code snippet.

    editor

    • Saving file as: Table or JS
      • Dragging a Table file will produce: y.use("store://execute key here","namespace here");
      • Dragging a Environment file will produce: y.env("store://execute key here");
      • Dragging a JS file will produce: y.include("store://select key here");
    • Saving file as: Environment
      • Dragging a Table file will produce: use "store://execute key here" as name_space;
      • Dragging a Environment file will produce: env "store://execute key here";
      • Dragging a JS file will produce:
        set change_var_name="store://select key here" on change_to_table;
  • Full screen layout
  • Sidebar which contains Sample templates, keys of a table, and a list of your files by type.
  • Changed file access FROM: tableid=id_here TO: id=id_here