Optional dependencies

Open
#142 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
scala
Domain
backend

Research direction

Start by reviewing the requested wireOpt[T] entry point and how the existing wire[T] behavior handles dependency resolution. Determine the intended semantics for enabled and disabled optional dependencies, then verify that the feature resolves to Some[T] or None as requested without breaking normal wiring.

Written by the indexing model from the issue text.

Description

Would it be possible to add feature which would allow to resolve optional dependencies?

Pseudo-implementation (which doesn't work):

  def wireOpt[T](enabled: Boolean): Option[T] = {
    if (enabled) {
      Some(wire[T])
    } else {
      None
    }
  }

Thanks for awesome library!

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from softwaremill/macwire

All issues in softwaremill/macwire

Similar issues

More Scala issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.