Vulcan/packages/telescope-releases/lib/server/publications.js

Meteor.publish('currentRelease', function() {
  if(Users.is.adminById(this.userId)){
    return Releases.find({}, {sort: {createdAt: -1}, limit: 1});
  }
  return [];
});
bringing packages back into core repo after all 2015-04-22 07:50:11 +09:00			`Meteor.publish('currentRelease', function() {`
namespacing user roles 2015-04-27 17:14:07 +09:00			`if(Users.is.adminById(this.userId)){`
bringing packages back into core repo after all 2015-04-22 07:50:11 +09:00			`return Releases.find({}, {sort: {createdAt: -1}, limit: 1});`
			`}`
			`return [];`
Improve jsHint consistency This commit touch a lot of lines of code with the goal to be more rigorous about JavaScript code conventions defined in the `.jshintrc`. Some modification: * Add a list of used global symbols in the corresponding section of `.jshintrc` * Use local variables instead of global in a lot of places where the keyword `var` was mistakenly forgotten * Add missing semi-colons after instructions * Add new lines at the end of files * Remove trailing whitespaces * Use newer name of some Meteor APIs, eg `addFiles` instead of `add_files` * Add missing `break` statements in `switch` blocks * Use `===` instead of `==` and `!==` instead of `!=` * Remove unused variables This commit should also fix a few bugs due to this lack of rigor. One example of that was the test `typeof navElements === "array"` that was never true because in JavaScript, `typeof [] === "object"`, we replaced this test by the `_.isArray` method provided by underscore. It might also fix some potential collision related to global variables. There is still plenty of work until Telescope code base passes jsHint validation, but at least this commit is a step in the right direction. 2015-05-01 18:22:00 +02:00			`});`