I have startet using a different linter (standard) in a new project. Also: No semicolons, indentation by 2 spaces and more.
Other projects still use jshint. And a different style: with semicolons, indentation by 4 spaces and more.
When I open an old project the code is riddled with error messages as the different indentation and semicolons occur on every line...
I know how to set linter settings per project. But (how) can I activate / deactivate linters per project?
Related
Is there any way to highlight all lines which has code coverage for react app. I am using Jest. my editor is visual studio code.
You can use the vscode-jest plugin, it has codeLens (enabled by default).
Beware though, it's a little slow sometimes (on the first run especially). I disable 'run all on first load' option, to avoid that. The code coverage shown might be a little off sometimes due to these perf issues. But it works good enough for me most times. At the top of the file, it even shows the % of branches and line covered.
See related issue: https://github.com/jest-community/vscode-jest/issues/181
I've been working in a project since 3 months, at first was with Modern theme as default, after some changes I applied Indigo theme and kept working, yesterday tried to switch back to Modern without success, after several tries I followed step by step some directions another guy posted here : http://stackoverflow.com/questions/19820195/qooxdoo-how-do-i-create-a-new-theme-and-use-it-in-the-application surely I did something wrong because I didn't get Modern theme on, so, I undo everything. Now if I try to generate source I get many errors about resources and directories already deleted, my guess is that something is left at cache or somewhere else. Please can you help to apply modern theme correctly or at least anything I can continue working. Any help will be much appreciated.
If you just want to see the modern theme in your app without alterations, edit your config.json to include the line
"QXTHEME": "qx.theme.Modern",
then run generate.
Note: This question will be changed to eliminate old question with lower rating.
I see AngularJS console errors as follows:
Lexer Error: Unexpected next character at columns 0-0 [#] in expression [#].
The problem now is how to locate the source of this error among thousands of lines of code?
Old Question:
NOTE: This is the old question, please ignore.
I was working with a sample application from ng-flow file upload. I then moved the developed parts to my colleague's environment who is using bootstrap for CSS. I noticed that the look and feel changed on from his environment.
I realized that my colleague is using this css file:
http://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css
and I am using the css file the came with the download:
http://netdna.bootstrapcdn.com/twitter-bootstrap/2.3.2/css/bootstrap-combined.min.css
and both work fine, but they have clear differences on how the look and feel and how layout is presented.
I included both, and it seems the application is still working fine, and the look and feel is now merged.
I am just wondering if there is documentation that explains the differences and how to decide which one to use.
Appreciate your feedback.
The reason they look different is that they're referring to different versions of Bootstrap - version 3.3.7 vs version 2.3.2. (The other difference is where the files are hosted.) 3.3.7 is more recent than 2.3.2.
Generally, you want to use the most recent version available for whatever libraries you're including, unless you need to stay compatible with an older one. You shouldn't include both, though; that's going to have your users downloading a lot of redundant css.
Is there a way to limit the amount of omissions that Stylus allows? Particularly in a team environment, force the use of the pythonic layout with colons and semicolons.
I cannot find any documentation on configuring compilation.
Apparently there's no way to force this behavior when compiling with Stylus.
It's syntax is almost identical as SASS, you should consider using it.
Forcing code style is not a responsibility for Stylus. The situation with team environment to keep code style consistent is exactly why linting tools were created for and are commonly used for Javascript (ESLint, JSLint), CSS, SCSS etc.
For Stylus there is Stylint. Use it as a CLI tool, Git hook or in your Continous Integration service. There are also plugins with integrations for popular IDEs:
Atom
Sublime Text
WebStorm / PhpStorm / IntelliJ IDEA
Visual Studio Code
I'm having issues with Silverlight 4 Out-Of-Browser, as specified in the title.
What I did:
Update project settings to enable Out-Of-Browser. This enabled OOB, but when I ran the app in this way it just displayed a white screen.
What I have done to try to fix this:
All references to the System.Windows.Browser.HtmlPage (to avoid DOM interaction) have been removed as per various sources including this SO question and this blog post.
Remove any references to SizeChangedEventHandler as per this SO question.
Clean projects/solution, including ideas such as deleting *.suo files as per this blog post
Uninstalling the installed OOB app, reinstalling
Also:
As commented on by "kobruleht" here, attempting to attach the debugger does not appear to work. Visual Studio (2010, SP1) reports that it is attached without help from me, but breakpoints are not being hit.
And so:
Can anyone advise on other courses of action? At the very least I'd like to be able to step through and hit breakpoints (or even break on Exceptions!)
OK, I have a resolution.
In AppManifest.xml I specified assemblies to be loaded, one of these was not loading correctly, which meant that App.xaml.cs->App()was never reached. The problem is difficult to diagnose because the program runs, with no errors or exceptions, but then displays a white screen - quite misleading.
For anyone experiencing the same problem, the simplest debugging steps to take in this case is to run the app in in-browser mode, copy the results from the Output window, then compare the results from the Output window when you try to run in OOB mode. Any discrepancies will give a good hint to the problem.
I should also mention, that I have not had trouble with SizeChangedEventHandler as mentioned above.