We were writing out jsHintOptions with the `extends` attribute, which
wasn't working when loaded into the browser. Now the build process
loads the primary jshint file and modifies is to match the gallery
in order to write out a complete jsHintOptions object.
This could probably be a little more robust (since not all changes
to Apps/Sandcastle/.jshintrc get reflected automatically jsHintOptions,
but I doubt that will be an issue given that these files will rarely change.
Because jshint-eclipse does not support multiple `.jshintrc` files, I've
updated the root .jshintrc to include jasmine. This is then set to
false in lower-down `.jshintrc files using the extends capability.
This has the added benefit of meaning we no longer write out .jshintrc
files as part of the build step.
The only downside here is that jsHint in Eclipse thinks Jasmine globals
are okay in all of our Source files. However, that's not a big deal
and travis and our own jshint build step will detect the problem if
someone tries to call jasmine outside of the Specs directory.
Sean Lilley
Peter Gagliardi
Matthew Amato