Ugly mistake using dojo.require

I had created a custom package with the name “my.seqctrl”, creating one is as easy as


dojo.provide("my.seqctrl");

my.seqctrl = function() {
   // object code in here
}

Now I included the package wrong and finding the bug took me way too long, I really got pissed. I only got the message:

my.seqctrl is not a constructor

But it is! What I did was calling dojo.require like this:


dojo.require("my.seqctrl.*");

Just watch out to never make this mistake. It looks so right but is so wrong and the error message just points you to the wrong place. I guess that is why the new dojo packages get included in the .* way.

RSS feed for comments on this post · TrackBack URL

Leave a Comment