Add Dimension-DI to Dependency Injection#1191
Open
akardapolov wants to merge 1 commit intoakullpp:masterfrom
Open
Add Dimension-DI to Dependency Injection#1191akardapolov wants to merge 1 commit intoakullpp:masterfrom
akardapolov wants to merge 1 commit intoakullpp:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dimension-DI occupies a unique niche among existing DI entries. Unlike compile-time frameworks (Dagger, Avaje Inject), it operates at runtime with automatic classpath scanning. Unlike heavier runtime frameworks (Guice, HK2), it avoids proxies, reflection, and bytecode generation entirely by leveraging the JDK Class-File API. This combination is unique among the listed libraries.
This project is developer-friendly (Apache-2.0 license, English documentation) and fills a gap for developers needing a minimal, zero-boilerplate runtime DI container without the overhead of larger frameworks. If it doesn't fully meet criteria (a)-(c), I believe its unique approach and function justifies inclusion under criterion (d).
Thank you for considering!