Thanks, Justin.
So, if I understood you properly, currently these errors are
expected at least.
Just want to note that these issues are not in my code (I'm
talking on your vary latest words about the way "how you access
properties") - these issues are reported on the code in TypeLib
projects. So, may be their code could be fixed somehow? Of course,
a user should take care of these things in his (her) own code, but
I'm talking not about a user's code - I'm talking about the
TypeLibraries themself.
My +1 for possibility to lower the severity for these errors in
case of "literal fields with a dash" and similar issues.
Thanks in advance,
Victor Rubezhny
Exadel, Inc.
On 07/11/2013 10:48 PM, Justin Early wrote:
Hi Victor,
Thanks for reaching out.
There are a couple of problems here (we may need to change
default severity)
1. Object literal fields with a dash can not be accessed
using dot (mytype.my-property) they must be accessed using
mytype['my-property'] -- this is issue where you have in
background-attachment. I am ok making this a warning by default
rather than error severity. Something we can relax and provide a
preference for folks who want to avoid this issue.
2. base is a reserved name in vjo.js so if you name a
method/property in a vjo type base we produce an error. In the
case of metatypes we can relax this rule. So if you have
options({metatype: true}) in the meta type we can skip over this
rule.
3. class is a reserved word in _javascript_ so you will get
error for this one. If you use the class name in an object
literal we have to use class as a string "class" to bypass this
exception. I will take a look at swfobject2 and see if we can
fix this using string "class" rather than class as an
identifier.
https://code.google.com/p/swfobject/wiki/documentation
4. bottom property error I am not sure about that one. Will
need to dig into that one. Btw. The ExtJs type library is no
longer being updated here. Sencha produces their own type
libraries with the Sencha Eclipse Plugin.
Justin
Some of these are due to errors that happen due to how you
access properties
Hi guys!
Does anybody can see the same problems in TypeLib projects I
can see:
Description Resource Path Location Type
"Invalid identifier: "bottom"" Element.js
/ExtCoreTL/src/com/sencha/extcore line 49 VJET Problem
Description Resource Path Location Type
"Invalid identifier: "background-attachment""
DojoAuxiliary.js /DojoTL/src/org/dojotoolkit line 67
VJET Problem
Description Resource Path Location Type
"Invalid identifier: base" SwfObject.js
/SWFObjectTL/src/com/google/swfobject2 line 95 VJET
Problem
Description Resource Path Location Type
"Invalid identifier: class" SwfObject.js
/SWFObjectTL/src/com/google/swfobject2 line 82 VJET
Problem
Is this a known issue or something new?
Don't remember is this something new or not (or may be I
have misconfigured something?), but as for now, when I'm
getting the TypeLib projects from git (git://git.eclipse.org/gitroot/vjet/org.eclipse.vjet.typelibs.git)
and adding these projects to my VJET Project, I see these
errors in Problem View (as well as in the according editor).
Thanks in advance,
Victor Rubezhny
Exadel, Inc.
PS: Eclipse Kepler 4.3R + VJET nightly build
_______________________________________________
vjet-dev mailing list
vjet-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/vjet-dev
_______________________________________________
vjet-dev mailing list
vjet-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/vjet-dev
