- This topic has 8 replies, 6 voices, and was last updated 18 years, 5 months ago by support-eugene.
-
AuthorPosts
-
Todd MainMemberI have been forced to disable the JavaScript validations because they are validating JavaScript in a directory that I have no control over and spitting out a bunch of errors.
That is, I work on a large project where the directory structure is fixed (and written in stone), and there is a subdirectory that contains “Robohelp” source code that is provided by another team.
If it were Java source, I could exclude that directory from the java compiler and therefore I would not get errors.
However, the MyEclipse validators (JavaScript in this particular case) have no such filters that I can find. This seems like a really easy feature to add to all of your validators (unless it’s already there and I just can’t find it!)
Riyad KallaMemberTry right clicking on the directory, going down to Properties, checking “Derived” and then hitting OK. Then be sure to do a right click on project root > MyEclipse > Remove ALl errors Markers and possibly rebuild the project to re-sync all the markers.
Todd MainMemberThanks, that helped. However, I’m noticing that the JavaScript validator creates so many warnings for our “real” JavaScript (which all works) that I’m just turning off JavaScript validation. The most common seems to be complaints about references to browser variables. Our code uses the simple approach to testing for things, like this:
if (window.whatever) {
window.whatever();
}I get a warning from the validator when I test the variable. I think that the warnings might be nice if JavaScript were a controlled language, but since there is so much variation in how to do things, the warnings are just annoying, and I’m certainly not going to rewrite all of our javascript just to make warnings go away.
My biggest complaint with Eclipse (and MyEclipse, as a result), is that I can’t right-click on a particular error/warning message in the “Problems” pane and tell Eclipse/MyEclipse to suppress that particular warning. The preferences to enable/disable particular validations are generally too broad to help. That is, I don’t want to disable an entire category of validations: I just want to turn off one among many in that category, and I want to do it in the most obvious place, which is the window where the warning messages appear. Trying to pair up the warning message with a particular preference is a frustrating excercise in trial and error.
Riyad KallaMemberWe are sorry that you ran into this and I agree, a behavior like you describe would be very nice to have.
We also have an enahncement filed to provide more fine-tuned control of the validators in general. It’s not a small or easy task which is why we haven’t done it and throw it into one of the incremental builds.
jdh2550MemberFWIW, I second the request for finer grained control of the JavaScript validator. But I’ve only been using MyEclipse for a couple of days – but I like it 🙂
rogue_devMemberI would like to add my vote also. At least the ability to have the validator ignore warnings.
Because the formatter will not complete if there are ANY validation warnings or errors, it means that I cannot format the code.
carypMemberAnother warning that I need to supress comes up when a function is not terminated by a semi-colon. For example:
myNs.foo = function(){ //this function does not have a semi-colon after the '}' } myNs.bar = function(){ //this function does };
I will get a warning stating something like:
“Expected ‘;’ and instead saw ‘myNs.bar'”
I thought disabling strict line ending would make this go away. Should it?
-CP
Riyad KallaMemberI’m not positive what that option translates too, I’ll check.
support-eugeneMember@rogue_dev wrote:
Because the formatter will not complete if there are ANY validation warnings or errors, it means that I cannot format the code.
Currently formatter can format only the code that is correct, so we cannot remove validation before formatting atm 🙁
-
AuthorPosts