Awesome!

[ogix]

I've accidentally found your article about this new library. It looks awesome in the example. Is this library going to be maintained as there were no commits recently? Are there any limitations currently? I hope it will have a future!

[antischematic]

Hi @ogix. I haven't been active recently but I still plan to work on this. Limitations mentioned in the readme are a blocker for the current implementation so I'm going to make a few changes. Happy to discuss if you're interested.

[ogix]

Glad to hear that you plan to work on this! BTW have you seen this repo before https://github.com/HafizAhmedMoon/ngx-hooks ? It is archived now but maybe you can get some ideas/code from it. I see that it was trying to implement something similar but in a different way.

[antischematic]

I've pushed up my latest iteration on the API that doesn't rely on compiler quirks. The only "private" api being used now is directiveInject, which Angular team has said will effectively become public in the future, so I'm removing the disclaimers and moving forward with this new version that I hope is also simpler to use.

[ogix]

Cool! I love the new approach as it is cleaner and reminds me of react hooks :) I will try playing around later and see how it works and also will look at the code to better understand the concept.
BTW it looks like the Service example is not complete as there is no user and userId defined.

[lennerd]

Hi @mmuscat, I definitely have to echo @oyix! What you got going on here in such a short time and with such good quality is really impressive.

And to be honest, I'm really exited about this.

After a few good years of React development, I've had the "privilege" of working on a few Angular projects for a while now. Since then, I've been regularly browsing for solutions to the many problems I'm having with Angular. Like how to really compose components, how to make UI logic more reusable, how to deal with the many quirks Angular can have when it comes to content projection and asynchronous code etc.

When googling for the problem, they always say Angular doesn't need React hooks. Services and reactive programming would have solved the problem long ago. Hardly anyone seems to really understand, that hooks are about so much more than reusing UI logic. They are about the composition of UI logic and thus finally the real composition of components, without mixins or ugly inheritance. Too bad the comments on your detailed RFC don't seem to understand this.

To make a long story short: keep it up! Especially the boundary, store and query packages are a super exciting direction!

Is there any way, any part of the project where we can help, support you and the project?

[antischematic]

@lennerd Thanks for the support, best way to help is to test it in a real project and report any issues so they can be fixed, or contribute to the RFC.