Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Separate API classes into separate modules from implementations #96

Copy link
Copy link
@jboynes

Description

@jboynes
Issue body actions

When using injection, application code would generally not need to interact with the implementation classes. For example, it would receive a Datastore or Storage instance directly and never need to interact with any of the factory or ServiceOptions classes e.g.

class MyApp {
  @Resource Datastore dataset;
  @Inject Bucket data;
  void doSomething() {
    // just use dataset and data fields ...
  }
}

By separating the API classes that it would use into a separate jar, the user can avoid having a dependency on the implementation itself and on any of the libraries that the implementation happens to use.

Metadata

Metadata

Labels

🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.