Mark project as abandoned #2040
Conversation
|
Hi, @martinsotirov why you think it will never be compatible? What is the issue with the architecture? can you please elaborate a little more? We are trying to keep this project alive since we are using it in some of our applications. We even created a fork and published some ng14 compatible packages. But didnt went for the ng15 migration yet . Thanks! |
|
@aotaduy, I state the reason in my change to the README:
Due to the fact that Ivy is Angular's only rendering engine since v15, this project would require a considerable rewrite. Also the author isn't interested in maintaining it or even accepting PRs. If you manage to get it working on Angular v15+, I'm sure many people (myself included) would be interested in using your fork. |
|
I understand that the author is not intrested, but not sure why The ivy engine would require so many changes. We have only migrated to ng14, but in the near future will try to make it work with Ivy. Will come back then. I've seen some pull requests that migrtated to 15 but they only changed the angular version. Looks like this is not enough right? Thanks for your response ! |
|
Hi @martinsotirov i just made a new version with angular 15 and tested in our app, looks like is working fine. you can find the packages here Made a stackblitz test and it also works fine |
No description provided.