Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You have a mismatch in the version used to compile the <code>Handlebars</code> templates and the version included via the script tag.</p> <p>If you are using <code>grunt-contrib-handlebars</code>, it uses the npm module handlebars to compile the the templates. The handlebars module/project is independent of Ember and has its own revisions that may or not be compatible with Ember.</p> <p>To maintain compatibility with Handlebars Ember needs specific versions of handlebars which it is warning you about.</p> <p>The tricky part here is you need to ensure that <code>grunt-contrib-handlebars</code> is forced to use that specific version of handlebars. </p> <blockquote> <p>Solution 1: Use <a href="https://npmjs.org/doc/shrinkwrap.html" rel="nofollow">shrinkwrap</a> to change grunt-contrib-handlebars's handlebars dependency version.</p> <p>Solution 2: This is what I am currently using. I have switched to <a href="http://www.emblemjs.com" rel="nofollow">Emblem</a>. The emblem grunt task asks for your handlebars file explicitly so you don't have to drop down to node sub dependency management. And your build includes the same file into your script tags, thus avoiding duplication/mismatch for future revisions.</p> </blockquote> <p>Edit: After Gruntfile edit</p> <p>Looking at the Gruntfile I don't see anything amiss. Looks like a standard build process, <code>js -&gt; neuter -&gt; (if prod) -&gt; uglify</code> etc.</p> <p>I think you need to try refreshing both emberjs and handlebars js files. Try using the files from the starter kit itself, those definitely work together.</p> <p>And verify this for your index.html by looking at the unminified source in Chrome/Inspector. Handlebars has the revision numbers below the banner something like <code>Handlebars.VERSION</code> and <code>Handlebars.COMPILER_REVISION</code>. Match those with what you see in the ember.js file, somewhere below <code>@submodule ember-handlebars-compiler</code> in the <code>Ember.assert</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POEmber.js - Handlebars not recognized if required via Grunt (Node.js)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDarshan Sawardekar
    1. USDarshan Sawardekar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COthanks for your answer, but I'm not using the `grunt-contrib-handlebars` plugin as I'm not precompiling my templates in the buildstep. So I'm able to say that the different `Handlebars` versions in `grunt-contrib-handlebars` don't have an effect on my issue.
      singulars
      1. PO
      1. USherom
    2. COI can't think of anything else that could cause this other than the version mismatch. Maybe you could post your Gruntfile, might clarify things.
      singulars
      1. PO
      1. USDarshan Sawardekar
    3. COI added my `Gruntfile.js` in the first post ;)
      singulars
      1. PO
      1. USherom
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload