Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add VERSION property to CanJS Object #316

Merged
merged 4 commits into from Apr 26, 2013
Merged

Add VERSION property to CanJS Object #316

merged 4 commits into from Apr 26, 2013

Conversation

ccummings
Copy link
Contributor

For detecting what version is loaded.

What about adding this to can.js:

can.VERSION = "1.1.4";

The grunt build scripts would have to be updated to keep this in synch with the version in package.json

@ccummings
Copy link
Contributor Author

Wasn't sure what we wanted to do about the VERSION property when using CanJS from GitHub. The version will be @VERSION, which isn't very helpful, but we require some sort of unique symbol that can be replaced when the grunt build task runs.

Alternatively, we could just update this property manually in the source, but I would prefer to automate as much as possible.

@ccummings
Copy link
Contributor Author

Changed the default value to @EDGE. This lets developers using the GitHub version know they are using the bleeding edge version of CanJS.

{
pattern: /@EDGE/gim, //version property
replacement: '<%= pkg.version %>'
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove the tailing comma? I guess it's one of my pet peeves but it shows up as an error in Webstorm and any JS linter.

daffl added a commit that referenced this pull request Apr 26, 2013
Add VERSION property to CanJS Object
@daffl daffl merged commit cdb8d96 into master Apr 26, 2013
@daffl daffl deleted the issue-316 branch April 26, 2013 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants