-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Disenguage AngularJS and migrate to VueJS #211
Comments
Technically, I would take way more pleasure working with VueJS. Big refactor work ahead though ! Material design is nice about form input : it keeps them visually light. Some exambles can be seen here : https://vuetifyjs.com/en/components/text-fields/#usage I think it encourages us to reconsider the current modal edition design (with edit / save buttons toggling between two displays) in favor of simpler form views, always in « edit » mode. That is just my opinion :). |
Is there any schedule for this rework ? I'd like to contribute to this repository, but what is repelling me is the AngularJS framework. What is the motivation for the migration to VueJS over Angular 2+ ? |
Angular2+ is obsolete, and if we want to solve the technical debt we have to use the last version of Angular (when I'm writing this comment is Angular 11.x). It requires to rewrite all the JS app. |
By talking about Angular 2+ I was talking about Angular 2, 3, ... 8,... 11 :) I was working on my fork to refactor the existing js code to follow Angular 1 guidelines which is a tremendous help to achieve the single responsibility principle and cut down to services, controllers, factories, etc to see better what is to convert (in Angular or Vue) But if you tell me that the migration began in internal, then maybe there is no purpose to do so anymore. |
Allow to :
The text was updated successfully, but these errors were encountered: