-
Notifications
You must be signed in to change notification settings - Fork 105
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
Upgrade to Angular 1.5 #90
Labels
Comments
As we are adding component in the system which is only compatible from angular 1.5.X we should migrate. |
Once #95 lands, this issue will be closed. |
jniles
referenced
this issue
in jniles/bhima
Jan 8, 2017
This commit fixes the user experience problems reported on the cash form. A clear button allows the user to clear all form data in a uniform place that users would expect. Closes #90.
jniles
referenced
this issue
in jniles/bhima
Jan 9, 2017
This commit fixes the user experience problems reported on the cash form. A clear button allows the user to clear all form data in a uniform place that users would expect. Closes #90.
jniles
referenced
this issue
in jniles/bhima
Jan 9, 2017
This commit fixes the user experience problems reported on the cash form. A clear button allows the user to clear all form data in a uniform place that users would expect. Closes #90.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Angular 1.5 was just released. The most significant advantage is first-class support for
angular.component()
which we should seriously consider implementing anywhere we would use a directive (and potentially re-writing some of our old directives as components).Both the changelog and migration guide seem to suggest that we will not have any breaking changes - only security and potentially performance improvements.
The text was updated successfully, but these errors were encountered: