Calculator App | SASS | Angular 18| Signals based state management

What are you most proud of, and what would you do differently next time?

The core point of this project was the management of the logic, even if I didn't use NgRX I let myself be guided by its core concepts to manage the state of the application within a service that provide the state and handle its changes.

What challenges did you encounter, and how did you overcome them?

All the actions that modify the state are managed within the service that exposes a single action to the smart app component and this favors a decoupling between the application logic and the access of the data and the rendering in dumb components. The service acts like a Facade that expose the state and handle events by actions dispatched from components by UI events.

What specific areas of your project would you like help with?

I would love to get some feedback from you. Your insights would be incredibly valuable in helping me improve. Here are a few specific areas where I'd appreciate your thoughts:

• Folder Structure Management:

How effective is the current folder structure? Are there any changes you would suggest to improve organization and maintainability?

• State Design and Action Management:

What do you think about the design of the state and the way actions are managed? Are there any best practices or improvements you would recommend?

• SCSS Organization:

How is the SCSS part of the application organized? Do you have any suggestions for better structuring or optimizing the SCSS?

• Possible Improvements or Suggestions:

Do you have any general feedback or suggestions for improving the solutions I've implemented? Are there any areas where you see potential for enhancement?

Thank you so much for taking the time to review my work. Your feedback is greatly appreciated ❤️.

Happy code to everyone!! 😁