Linting should ignore plato output

[arobson]

This pretty much breaks the build after a coverage report has been generated because Plato does lots of naughty things (according to our settings).

[Prestaul]

@arobson you can always configure biggulp to ignore those files:

require("biggulp")(gulp, {
    exclude: [ "!node_modules/**", "!coverage/**", "!plato/** ]
});

Biggulp ignores the coverage directory because it sets up coverage reporting. It doesn't pull in or configure plato, do you think it makes sense to add ignores around things biggulp itself isn't using?

[arobson]

@Prestaul - perhaps the plato folder is from an old version of this? I don't have anything that would tell it to put the output in that folder instead of coverage. The goal is to make it "just work" without additional config for projects that follow the conventions.

I would expect linting to only happen for source and spec folders. At one point, biggulp had defaults for what these were. I'd expect it to only lint files it knew about vs. the whole top-level folder.

[Prestaul]

@arobson, I see what you mean. I think this changed because it meant that other project files (e.g. the gulpfile, and the resources, client, server directories in some of our projects) weren't getting linted. We should also keep in mind that a very large number of javascript projects outside of LK put source code at the root or in other directories (e.g. lib and test are very common).

We could set this up so that the default only lints in directories commonly used at LK, or we could set it up so that it lints all js files by default. I think I'd prefer to see too many errors by default and have to exclude files than to have potential issues hidden from me by default. Of course, if the goal is that this tool will help force us to bring more consistent structure to our projects then that puts another spin on it... What are your thoughts?

[arobson]

@Prestaul - as with most of our projects, we tend to pick conventions that align with what we're using internally. The configuration options are still there, but I'd like to see our stuff work without tweaking when devs follow the conventions. It's a nice way to reinforce them and cuts down on the amount of fiddling/tweaking needed to get something started.

We can eventually update this project to do that. The README should also get updated since the common gulp thing cleans up what you actually need in your gulpfile a lot.