This file is meant to be a unique identifier for a project and is generated automatically in new (Meteor) projects. Since VulcanJS is instead cloned as a boilerplate for a new application, this is less ideal since each project receives the same unique identifier. The reason this is not ideal is explained within the comment of the removed file:
e634907530/.meteor/.id
Most importantly, this affects the ability to see any sort of traction on `vulcan:*` packages in Atmosphere since they are aggregated together. This means that 10 or 1000 installs might just be tracked as 1!
* Revert "add note link to issue in collection2 on mutation insert, remove debug console logs on mutation edit"
This reverts commit 7a15103de7.
* Revert "node simpl-schema + collection2-core: fix vote by specifying the right type of the array (dont use blackbox in the end!)"
This reverts commit e894c3224c.
* Revert "add graphql date type (fix problem with node simple schema), fix an update bug on date picker, add edit check on custom post item, add `blackbox: true` for arrays field (validation problem with simple-schema)"
This reverts commit 9d84fbec98.
* Revert "use node `simpl-schema` by aldeed to replace `meteor/aldeed:simple-schema` ; use the meteor collection2 core package as recommended"
This reverts commit 016935f4fa.
* revert before node-simple-schema, fix obj.hasOwnProperty undefined error thrown by simple-schema & collection2
* CustomPostsItem: check on renderActions; withDocument/List: pollInterval 20seconds by default; DateTime form component enhancement + GraphQLDate type
