[INFRAUTILS-63] Guice Inject utility ideas Created: 30/Jan/19 Updated: 04/Feb/19 Resolved: 04/Feb/19 |
|
| Status: | Resolved |
| Project: | infrautils |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Michael Vorburger | Assignee: | Michael Vorburger |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
infrautils.inject
class ModuleBuilder { Module build(); // ignore duplicates, auto inject ClasspathScanner addModule(Class<Module> moduleClass); addPackage(String packageName); |
| Comments |
| Comment by Michael Vorburger [ 04/Feb/19 ] |
|
It occurred to me, with a few days distance, that any such "magic" like what I imagined above, would make error tracking for Guice DI much more difficult than with today's still (once you are used to them) clear errors... Guice points out which Module what binding is from - but it could not do that anymore if we did above, so I think this is actually NOT a good idea - so closing this. |