Alasdair Smith 154943ba68 Don't check for linting errors if code check is disabled ... There are a couple of reasons for this: 1. Some linting errors are returned from the server after a compile is run, replacing client-side linting errors. If code check is disabled this does not happen, and therefore linting errors persist until the next compile. This makes it appear as though autocompile is not running 2. It is likely that if code check is disabled, the user is deliberately ignoring linting errors and therefore the linting check is pointless		2017-11-17 16:38:44 +00:00
..
analytics	pulled tempaltes search into its own file	2016-03-22 22:29:18 +00:00
directives	Enforce stricter password policy.	2017-07-24 11:06:47 +01:00
filters	include moment in package versions	2016-10-05 14:54:42 +01:00
ide	Don't check for linting errors if code check is disabled	2017-11-17 16:38:44 +00:00
main	Merge branch 'master' into sk-unlisted-projects	2017-11-02 10:10:09 +00:00
modules	redirect to /login on failed requests	2016-11-04 16:03:18 +00:00
services	Use standard promises with the http service.	2017-06-20 11:50:23 +01:00
utils	Add basic change tracking into editor behind a feature flag	2016-10-10 17:06:46 +01:00
base.coffee	Remove commented-out code	2017-10-02 14:50:43 +01:00
ide.coffee	Add a general 'ide:loaded' event, to init popover	2017-11-09 15:12:55 +00:00
libs.coffee	Use promise method signatures, instead of old HTTP service ones.	2017-06-20 16:04:06 +01:00
main.coffee	Relocate qProvider setup.	2017-07-03 11:19:13 +01:00