nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Warnings now appear as Errors - was a way to suppress

HFCDev

Hi,

In CSIDE, I have a module recently exported from CS 10.0 and we're going to be using the source tree we are now managing in CS 10.5 as the single source of truth going forward. There are a bunch of items that now give errors where as before they gave warnings. All of them are non-fatal errors, and are OscriptProblemMarkers. Is there a way to suppress these, or at least have them appear as warnings? Yes, I get it, the Oscript language is changing, and we need to change our code, but this is code that I was able to suppress these errors on about two versions ago. Once we have this base build, we can go in and fix the warnings by adjusting the source as required but as a short term measure, I need to have it not throw compile errors for non-fatals.

-Hugh

Find more posts tagged with

Comments

Hany Samuel

CSIDE has nothing to do with errors or warnings, they comes directly from compiler inside the content server so if you see error then this code will not compile for this content server regardless of cside is there or not. Turning off errors/warnings on cside is not an option now but that being said seeing the error markers is not the issue to worry about here, the real issue is that code will not compile for this content server that you use as OTHome (if you do see errors not just warnings).

You can share specific code or errors you see and twe can work with you to see the way out of it.

Thanks,

HFCDev

Has there been a change introduced that would make a piece of code that did compile in, say CS 10.5 U 2017-03 not compile in CS 10.5 U 2017012?

-Hugh

Hany Samuel

Nothing jump to my mind, but I can not state facts in general we need to talk for specific cases. If you like to share the specific error you see and the code that kicks it, we can work it from there.

Thanks

Thomas_Gessner

I actually do have a follow up Question on this topic. I totally understand that there is no way to suppress Errors. But is there also no way to suppress a Warning?

For example something like "#@UnusedVariable" in Python or '@SuppressWarning("unused")' in Java. The compiler does not produce a warning then.

This would especially be very usefull for the Warning "Variable is written to but never used" because sometimes it is necessary to allocate the result of a function to a Variable just for debugging purpose. And much more usefull it would be for overridden obejcts. Because here the compiler complains about every feature you use in the code because obviously the features are not available in the object itself (e.g. "unknown feature this.fName referenced").

Regards

Tom