Dagger 2 java это

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

A fast dependency injector for Android and Java.

License

google/dagger

This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Sign In Required

Please sign in to use Codespaces.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching GitHub Desktop

If nothing happens, download GitHub Desktop and try again.

Launching Xcode

If nothing happens, download Xcode and try again.

Launching Visual Studio Code

Your codespace will open once ready.

There was a problem preparing your codespace, please try again.

Latest commit

This CL fixes an issues in our GitHub Actions where we are consistently going over our cache limit. Typically, we would need to clean out the cache manually at https://github.com/google/dagger/actions/caches. This script automates that process by deleting caches each run. - For a PR that is already closed: deletes all corresponding caches. - For duplicate caches with the same Git reference and cache key: deletes the older cache. The script should be idempotent, so I decided to run the script both at the beginning and end of each workflow. This ensure that the caches are cleaned up after a workflow ends, but also that we don't start accumulating unnecessary caches when a workflow fails before the script can be run. RELNOTES=N/A PiperOrigin-RevId: 551349636

Git stats

Files

Failed to load latest commit information.

README.md

A fast dependency injector for Java and Android.

Dagger is a compile-time framework for dependency injection. It uses no reflection or runtime bytecode generation, does all its analysis at compile-time, and generates plain Java source code.

Dagger is actively maintained by Google. Snapshot releases are auto-deployed to Sonatype’s central Maven repository on every clean build with the version HEAD-SNAPSHOT . The current version builds upon previous work done at Square.

You can find the dagger documentation here which has extended usage instructions and other useful information. More detailed information can be found in the API documentation.

First, import the Dagger repository into your WORKSPACE file using http_archive .

Note: The http_archive must point to a tagged release of Dagger, not just any commit. The version of the Dagger artifacts will match the version of the tagged release.

# Top-level WORKSPACE file load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") DAGGER_TAG = "2.47" DAGGER_SHA = "154cdfa4f6f552a9873e2b4448f7a80415cb3427c4c771a50c6a8a8b434ffd0a" http_archive( name = "dagger", strip_prefix = "dagger-dagger-%s" % DAGGER_TAG, sha256 = DAGGER_SHA, urls = ["https://github.com/google/dagger/archive/dagger-%s.zip" % DAGGER_TAG], )

Next you will need to setup targets that export the proper dependencies and plugins. Follow the sections below to setup the dependencies you need.

First, load the Dagger artifacts and repositories, and add them to your list of maven_install artifacts.

# Top-level WORKSPACE file load("@dagger//:workspace_defs.bzl", "DAGGER_ARTIFACTS", "DAGGER_REPOSITORIES") maven_install( artifacts = DAGGER_ARTIFACTS + [. ], repositories = DAGGER_REPOSITORIES + [. ], )

Next, load and call dagger_rules in your top-level BUILD file:

# Top-level BUILD file load("@dagger//:workspace_defs.bzl", "dagger_rules") dagger_rules()

This will add the following Dagger build targets: (Note that these targets already export all of the dependencies and processors they need).

deps = [ ":dagger", # For Dagger ":dagger-spi", # For Dagger SPI ":dagger-producers", # For Dagger Producers ]

First, load the Dagger Android artifacts and repositories, and add them to your list of maven_install artifacts.

# Top-level WORKSPACE file load( "@dagger//:workspace_defs.bzl", "DAGGER_ANDROID_ARTIFACTS", "DAGGER_ANDROID_REPOSITORIES" ) maven_install( artifacts = DAGGER_ANDROID_ARTIFACTS + [. ], repositories = DAGGER_ANDROID_REPOSITORIES + [. ], )

Next, load and call dagger_android_rules in your top-level BUILD file:

# Top-level BUILD file load("@dagger//:workspace_defs.bzl", "dagger_android_rules") dagger_android_rules()

This will add the following Dagger Android build targets: (Note that these targets already export all of the dependencies and processors they need).

deps = [ ":dagger-android", # For Dagger Android ":dagger-android-support", # For Dagger Android (Support) ]

First, load the Hilt Android artifacts and repositories, and add them to your list of maven_install artifacts.

# Top-level WORKSPACE file load( "@dagger//:workspace_defs.bzl", "HILT_ANDROID_ARTIFACTS", "HILT_ANDROID_REPOSITORIES" ) maven_install( artifacts = HILT_ANDROID_ARTIFACTS + [. ], repositories = HILT_ANDROID_REPOSITORIES + [. ], )

Next, load and call hilt_android_rules in your top-level BUILD file:

# Top-level BUILD file load("@dagger//:workspace_defs.bzl", "hilt_android_rules") hilt_android_rules()

This will add the following Hilt Android build targets: (Note that these targets already export all of the dependencies and processors they need).

deps = [ ":hilt-android", # For Hilt Android ":hilt-android-testing", # For Hilt Android Testing ]

You will need to include the dagger-2.x.jar in your application’s runtime. In order to activate code generation and generate implementations to manage your graph you will need to include dagger-compiler-2.x.jar in your build at compile time.

In a Maven project, include the dagger artifact in the dependencies section of your pom.xml and the dagger-compiler artifact as an annotationProcessorPaths value of the maven-compiler-plugin :

dependencies> dependency> groupId>com.google.daggergroupId> artifactId>daggerartifactId> version>2.xversion> dependency> dependencies> build> plugins> plugin> groupId>org.apache.maven.pluginsgroupId> artifactId>maven-compiler-pluginartifactId> version>3.6.1version> configuration> annotationProcessorPaths> path> groupId>com.google.daggergroupId> artifactId>dagger-compilerartifactId> version>2.xversion> path> annotationProcessorPaths> configuration> plugin> plugins> build>

If you are using a version of the maven-compiler-plugin lower than 3.5 , add the dagger-compiler artifact with the provided scope:

dependencies> dependency> groupId>com.google.daggergroupId> artifactId>daggerartifactId> version>2.xversion> dependency> dependency> groupId>com.google.daggergroupId> artifactId>dagger-compilerartifactId> version>2.xversion> scope>providedscope> dependency> dependencies>

If you use the beta dagger-producers extension (which supplies parallelizable execution graphs), then add this to your maven configuration:

dependencies> dependency> groupId>com.google.daggergroupId> artifactId>dagger-producersartifactId> version>2.xversion> dependency> dependencies>

// Add Dagger dependencies dependencies < implementation 'com.google.dagger:dagger:2.x' annotationProcessor 'com.google.dagger:dagger-compiler:2.x' >

If you’re using classes in dagger.android you’ll also want to include:

implementation 'com.google.dagger:dagger-android:2.x' implementation 'com.google.dagger:dagger-android-support:2.x' // if you use the support libraries annotationProcessor 'com.google.dagger:dagger-android-processor:2.x'

• We use implementation instead of api for better compilation performance.
  • See the Gradle documentation for more information on how to select appropriately, and the Android Gradle plugin documentation for Android projects.

  If you’re using the Android Databinding library, you may want to increase the number of errors that javac will print. When Dagger prints an error, databinding compilation will halt and sometimes print more than 100 errors, which is the default amount for javac . For more information, see Issue 306.

  gradle.projectsEvaluated < tasks.withType(JavaCompile) < options.compilerArgs  "-Xmaxerrs"  "500" // or whatever number you want > >

  If you do not use maven, gradle, ivy, or other build systems that consume maven-style binary artifacts, they can be downloaded directly via the Maven Central Repository.

  Developer snapshots are available from Sonatype’s snapshot repository, and are built on a clean build of the GitHub project’s master branch.

  Copyright 2012 The Dagger Authors Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. 

  About

  A fast dependency injector for Android and Java.

  Источник

  Dagger 2 – это элементарно (Часть 1)

  Dependency Injection (инъекция или внедрение зависимости) — это зависимость одного класса от другого. т.е. для полноценной работы одного класса нужна инициализация другого(их) класса.

  Например, класс Car (автомобиль) не может работать без класса Engine (Мотор) который в свою очередь не может работать без класса Fuel (Топливо). Выглядит это так:

  class Car(private var engine: Engine) class Engine ( private var fuel: Fuel) class Fuel() < private val fuel = if(BuildConfig.DEBUG)< “benzine” >else < “diesel” >> 

  В данном примере класс Car зависит от класса Engine а тот в свою очередь от класса Fuel.

  Dagger 2 – введение

  Dagger это библиотека которая помогает реализовать «внедрение зависимости:. Это библиотека google. Подробную документацию можно получить тут.

  • Приходится писать меньше шаблонного кода.
  • Помогает структурировать зависимости.
  • Сильно упрощает работу когда зависимостей много
  • Код становится простым для чтения
  • Отсутствие подробной документации
  • Dagger пытается понять намерения разработчика при помощи аннотаций. Это усложняется когда он вас не правильно понимает
  • dagger генерирует код, ошибки в которых так же сложно определить

  Первое использование Dagger 2

  В первую очередь нужно добавить dagger в приложение. Знаю 2 методов как это можно сделать
  1. Открыть build.gradle (App) и добавить след.

  1.1 В самом верху в разделе объявления plugin

  1.2 в разделе dependencies

  версию dagger (dagger_version) указываю в разделе

  Если такого еще нет, раздел нужно добавить над разделом android.

  2. Добавить Maven репозиторий через Project Structure — Dependencies — Add library dependencies

  После синхронизации проекта мы готовы к внедрению зависимостей при помощи dagger.

  В первую очередь создадим классы Car, Engine и Fuel:

   class Car constructor(private var engine: Engine) class Engine constructor(private var fuel: Fuel) class Fuel < private val fuelType = if(BuildConfig.DEBUG)< "benzine" >else < "diesel" >> 

  Перед констракторами классов Car, Engine и Fuel добавим аннотация dagger Inject, тем самым дадим понять dagger что эти классы должны быть внедрены при необходимости. Получаем след.

  class Car @Inject constructor(private var engine: Engine) class Engine @Inject constructor(private var fuel: Fuel) class Fuel @Inject constructor() < private val fuelType = if(BuildConfig.DEBUG)< "benzine" >else < "diesel" >> 

  Dagger должен знать как создавать все объекты которые он должен внедрять. Для того чтоб перечислить все классы которые мы внедряем (Inject) используется аннотация Component которая объявляется для интерфейса (DaggerComponent).

   @Component interface DaggerComponent

  при объявлении методов компонента важны не названия методом а возвращаемый ими класс.

  На этом шаге нужно собрать проект (Build — Rebuild project). После этого dagger сгенерирует необходимые классы и фабрику для инициализации компонентов. Название фабрики будет совпадать с названием интерфейса в которой мы инициализируем классы для даггер за исключением того что будет добавлен префикс „Dagger“, т.е. на выходе получим класс DaggerDaggerComponent.

  // Generated by Dagger (https://google.github.io/dagger). package com.example.dagger2; public final class DaggerDaggerComponent implements DaggerComponent < private DaggerDaggerComponent(Builder builder) <>public static Builder builder() < return new Builder(); >public static DaggerComponent create() < return new Builder().build(); >@Override public Car getCar() < return new Car(getEngine()); >@Override public Engine getEngine() < return new Engine(new Fuel()); >@Override public Fuel getFuel() < return new Fuel(); >public static final class Builder < private Builder() <>public DaggerComponent build() < return new DaggerDaggerComponent(this); >> > 

  Все готово. Попробуем создать поле car типа Car в MainActivity:

  private var car: Car = DaggerDaggerComponent.create().getCar() 

  Запустив приложение можно убедиться что поле car инициализируется при обращении к нему

  Источник

  Читайте также:  Csv файл прочитать php файл