-
Notifications
You must be signed in to change notification settings - Fork 1k
Should we use dependency injection in Neo 3? #1042
Copy link
Copy link
Closed
Labels
DesignIssue state - Feature accepted but the solution requires a design before being implementedIssue state - Feature accepted but the solution requires a design before being implementedEnhancementType - Changes that may affect performance, usability or add new features to existing modules.Type - Changes that may affect performance, usability or add new features to existing modules.HousekeepingSmall enhancements that need to be done in order to keep the project organisedSmall enhancements that need to be done in order to keep the project organised
Metadata
Metadata
Assignees
Labels
DesignIssue state - Feature accepted but the solution requires a design before being implementedIssue state - Feature accepted but the solution requires a design before being implementedEnhancementType - Changes that may affect performance, usability or add new features to existing modules.Type - Changes that may affect performance, usability or add new features to existing modules.HousekeepingSmall enhancements that need to be done in order to keep the project organisedSmall enhancements that need to be done in order to keep the project organised
Hi @neo-project/core,
I think it would be good for this project if we can update it to use dependency injection. This will make the code more modular and more testable. We already did this in neo-sharp and it worked really well.
I did some brief research and it seems that dependency injection fits with Akka:
https://doc.akka.io/docs/akka/current/actors.html#dependency-injection
What do you think? Shoud we use our own dependency injection or use an existing framework? We could copy from neo-sharp.