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

update aurelia libraries #345

Merged
merged 1 commit into from
Dec 31, 2017
Merged

update aurelia libraries #345

merged 1 commit into from
Dec 31, 2017

Conversation

gheoan
Copy link
Contributor

@gheoan gheoan commented Dec 21, 2017

No description provided.

@krausest krausest merged commit 8926ea3 into krausest:master Dec 31, 2017
@krausest
Copy link
Owner

Thanks - results are here.

Versioning seems a bit confusing for aureliea. Is it correct to take the aurelia-framework version number as the leading version number?

Aurelia appears to support only non-keyed updates. Why is that the case? Do you have any input for #304?

@gheoan
Copy link
Contributor Author

gheoan commented Jan 22, 2018

@krausest Good question! All aurelia libraries follow semver, so all aurelia libraries specify their dependencies version using the npm caret notation. I have noticed aurelia-framework's version is bumped only when code inside aurelia-framework is changed. Unlike other frameworks not all aurelia libraries have the same version. Call it confusing or call it semver. I can't answer your question without knowing what do you want the leading version number to represent?

I am not familiar with the concept of non-keyed vs keyed so I can't answer that. Do you know any resource that explains the difference between these and the disadvantages mentioned in #304?

@krausest
Copy link
Owner

A good discussion regarding keyed or non-keyed can be found in #104 (comment) and #89

@gheoan gheoan deleted the aurelia-update branch August 9, 2019 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants