Discuss: Future of the library

[Luguito]

Angular Library ?

Currently, the SignalManager is in a file inside a componentitos project. How we should proceed to bring this manager to an external project, to production?

Should we create an Angular Library?
How are we gonna make this manager open to other technologies?

What are the next steps in mind to expand the functionalities?

[Alan-TheGentleman]

Hi !! first of all... THANKS FOR YOUR HELP AND INTEREST !!

With the updates I've made to SignalManager, now called GManagerService and hosted in the gentleman-signals-state-manager library, the situation is different.

To bring GManagerService to an external project and to production, you can directly install it from npm using npm install gentleman-signals-state-manager. This will allow you to import and use GManagerService as any other dependency in any Angular project.

GManagerService has been designed to be framework-agnostic. Although it's currently implemented for Angular, it could be easily adapted to any frontend library or framework by simply changing the base signal library.

As for expanding the functionalities, we're open to suggestions and contributions. Some possible directions might include adding more signal manipulation methods, features to improve performance with a large number of signals, or functionalities to work with signals in asynchronous contexts.

I hope this clears up your questions. If you have any more queries, please feel free to ask.