I was wondering if it's possible to force grunt to compile LESS even if there is an error?
The reason I ask is I'm outputting settings from the interface (Moodle) into less so that they can be changed by users. When I try to see a colour or do some math it throws errors because it's either expecting an RGBA value or a number value.
An example of the syntax would be:
div{background-color: rgba(0,0,0,~"[[setting:blockboxshadowalpha]]");}
This works fine if I put it directly into the compiled CSS but fails when using the rgba() function or doing something like the following:
a:hover{color: darken(~"[[setting:linkcolor]]", 20%);}
Related
(https://i.stack.imgur.com/8CYZz.png)
isparalleltomethod
How do I get thsi to compile properly. I am trying to determine that two lines are parallel and also trying to see if the denominators on the equation do not equal zero.
But struggling with how to use other.getP1(), etc.
Return method error
as well as the method error at the top
This is the latest version of my java file and I am not sure what else to do.
Getting warning from Script Checker : "OMEGA13 was used but was never set (will evaluate as its name)"
I've set
start using Omega13
-- some codes here --
stop using Omega13
Anyone has any idea on why the warning sign is there?
Eggplant documentation - Advance scripting: Error Recovery with Omega13
What's probably happened is somewhere you've mistyped some variant of omega13.
Sensetalk treats uninitialized variables as strings. This results in lots of hard to debug errors.
name = "my name"
put naame
This will print naame which is probably not what you wanted.
It looks like the correct form to invoke is omega13 not Omega13, or OMEGA13. I'd check the documentation and make sure that you haven't mistyped it anywhere.
You may also want to look into the strictVariables global which if true will treat using an uninitialized variable as an error.
I have a serious issue with a CMake project where I try to redefine a build number variable locally for a unit test, but it just failed once the real build number increased above the hardcoded one of my test.
After some testing, I am absolutely horrified to find that if I do:
set(MY_BUILD_NUMBER "3111")
add_definitions(-DMY_BUILD_NUMBER=${MY_BUILD_NUMBER})
...and later for my test I redefine it to a hardcoded value
add_definitions(-DMY_BUILD_NUMBER=3118)
The MY_BUILD_NUMBER in my test is 3111, which is logical.
But if I do:
set(MY_BUILD_NUMBER "3120")
add_definitions(-DMY_BUILD_NUMBER=${MY_BUILD_NUMBER})
...and later for my test I redefine it to a hardcoded value
add_definitions(-DMY_BUILD_NUMBER=3118)
The MY_BUILD_NUMBER in the code is 3120 and not 3118 anymore.
I could not find any documentation about this. Does anyone know what can cause such a unexpected behavior of CMake, or if it's just one more bug that to report...
Thanks !
No matter how I update the config file I seem to always end up with a space
System.assert(true); becomes System.assert (true);
This is only when the function is called assert
The following both format without a space before the '('
System.asser(true);
System.assertt(true);
Uncrustify config https://pastebin.com/4bnNXzhC
I believe your problem is that Java has an assert statement which Uncrustify's confusing your function call as. Although that wouldn't make much sense considering I tried to test if adding/removing spaces before control statements would change this behavior and it didn't.
I did find a workaround for you through the following configuration options parsing as Java. Since Java supports the assert statement it is a bit odd that they don't have a specific configuration option for it. It may be in your best interest to file a bug report / GH issue with the Uncrustify devs to help better resolve this problem.
# Add or remove space between the user function name and '(' on function
# calls. You need to set a keyword to be a user function in the config file,
# like:
# set func_call_user tr _ i18n
sp_func_call_user_paren = remove # ignore/add/remove/force
set func_call_user assert
Keep in mind that Apex is not an officialy supported language of Uncrustify. So if things don't work specifically for Apex then there's really not much else that can be done.
Short: I am looking for a way to get the text of the script that was evaluated and caused a syntax error from within the context of window.onerror.
Long:
The full scenario includes a phone gap application and the PushNotifications plugins.
When a push message is sent to the device a javascript error is caught using window.onerror.
with the text "SyntaxtError: Expected token '}'"
the reported line number is 1 (is it is usually when dealing with EVALuated code.
The way the plugin executs its code is by using:
NSString * jsCallBack = [NSString stringWithFormat:#"%#(%#);", self.callback, jsonStr];
[self.webView stringByEvaluatingJavaScriptFromString:jsCallBack];
I belive but not 100% sure that this is the code PhoneGap Build are pushing
more code can be seen in here https://github.com/phonegap-build/PushPlugin/blob/master/src/ios/PushPlugin.m#L177
the self.callback is a string passed by me to the plugin and jsonStr is (supposed to be) an object describing the push message.
when I tried to pass as the parameter that ends up being self.callback the string alert('a');// then I did get the alert and no syntax error. ad now I am trying to understand what does jsonStr gets evaluated to so that maybe I can find a way around it or figure out if its my fault somehow (maybe for the content I am sending in the push notification....)
I also tried to look at the last item of the $('script') collection of the document hopeing that maybe stringByEvaluatingJavaScriptFromString generates a new script block but that does not seem to be the case.
further more in the window.onerror I also tried to get the caller
using var c=window.onerror.caller||window.onerror.arguments.caller; but this returns undefined.
As I stated before - I am looking for ideas on how to determine what exactly is causing the syntax error possibly by getting a hold of the entire block of script being evaluated when the syntax error happened.