As you know, we no longer work on or maintain Ionic v1, except occasionally for enterprise users.
We are hopeful that Ionic 4 with web components will be usable by AngularJS users, as a way for those still on Ionic 1 to move into the future without having to move to Angular 5+. However, it's not a guarantee we'll be able to make that work as AngularJS has some of the worst web component compatibility of popular frameworks.
In the meantime, we are open to having a community maintainer or two work on this repo to handle issues and manage PRs. We don't want to leave everyone still on v1 out to dry, but the reality is we just don't have the resources to manage Ionic v1 anymore, not to mention it doesn't fit our new strategy of not binding tightly to frameworks and focusing on web standards (such as web components) instead.
If you are interested, feel free to comment on this issue or email me at max@ionicframework.com.
Hi,
As you know, we no longer work on or maintain Ionic v1, except occasionally for enterprise users.
We are hopeful that Ionic 4 with web components will be usable by AngularJS users, as a way for those still on Ionic 1 to move into the future without having to move to Angular 5+. However, it's not a guarantee we'll be able to make that work as AngularJS has some of the worst web component compatibility of popular frameworks.
In the meantime, we are open to having a community maintainer or two work on this repo to handle issues and manage PRs. We don't want to leave everyone still on v1 out to dry, but the reality is we just don't have the resources to manage Ionic v1 anymore, not to mention it doesn't fit our new strategy of not binding tightly to frameworks and focusing on web standards (such as web components) instead.
If you are interested, feel free to comment on this issue or email me at max@ionicframework.com.
Thanks!