Accessing wired instances within modules defined as classes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- scala
- Domain
- developer-experience
Research direction
Start by reviewing MacWire's module composition and lookup APIs, especially the UserModule, DatabaseConnectionModule, @Module, wiredInModule, and classOf[UserFinder] examples in the issue. Clarify the supported way to access a wired instance from composed class-based modules, and document the required setup and completion example for this use case.
Written by the indexing model from the issue text.
Description
I am new to Scala and Macwire and trying to figure out how to access instances that are wired using modules organized as classes. If modules are defined as traits, one can extend them and access the wired instances in them as below,
trait UserModule {
lazy val userFinder: UserFinder = wire[UserFinder]
}
class UserFinderSpec extends FlatSpec with UserModule {
assert userFinder.find(...) should ...
}
If my modules are organized as classes with composition, how do I access the instances?
class UserFinder(databaseConnection: databaseConnection) {
}
@Module
class DatabaseConnectionModule {
lazy val databaseConnection: DatabaseConnection = ...
}
@Module
class UserModule(databaseConnectionModule: DatabaseConnectionModule) {
lazy val userFinder:UserFinder = wire[UserFinder]
}
class UserFinderSpec extends FlatSpec {
//How to access UserFinder here?
//val wired = wiredInModule(new UserModule(new DatabaseConnectionModule))
//val userFinder = wired.lookup(classOf[UserFinder]
//Above way to access the instances seems complicated
//as I need to instantiate the modules with it's dependency chain which can be very long in my use-case.
}
- Dominant language
- Scala
- Stars
- 1.3k
- Forks
- 77
- Avg merge
- 9m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from softwaremill/macwire
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
softwaremill/macwire#412 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
softwaremill/macwire#391 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
softwaremill/macwire#301 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
softwaremill/macwire#281 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
softwaremill/macwire#278 · 3 comments ·
All issues in softwaremill/macwire
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ergoplatform/ergodocs#614 ·
-
area:ci enhancement requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/datafusion-comet#6078 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
[VL] madvise(WILLNEED) call fails in MmapFileStream because of wrong calculation of fetching length Openbug triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
chipsalliance/rocket-chip#3831 ·