Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider adding a no-op artifact #7

Closed
ColtonIdle opened this issue Mar 20, 2019 · 3 comments
Closed

Consider adding a no-op artifact #7

ColtonIdle opened this issue Mar 20, 2019 · 3 comments

Comments

@ColtonIdle
Copy link

There are a lot of libraries that can be used for debugging and they typically have a no-op artifact so you can decide to leave out the library easily where you would like to.

An example of this is leak-canary:

  debugImplementation 'com.squareup.leakcanary:leakcanary-android:1.6.3'
  releaseImplementation 'com.squareup.leakcanary:leakcanary-android-no-op:1.6.3'
@Dimdron
Copy link
Contributor

Dimdron commented Mar 20, 2019

@ColtonIdle We have no-op artifact but still didn't mention it in the documentation. We'll update docs soon 😉

@Dimdron
Copy link
Contributor

Dimdron commented Mar 20, 2019

@ColtonIdle we've updated our README

@Dimdron
Copy link
Contributor

Dimdron commented Mar 20, 2019

You can use noop artifact in this way:

dependencies {
    debugImplementation "com.appspector:android-sdk:1.+"
    releaseImplementation "com.appspector:android-sdk-noop:1.+"
}

@Dimdron Dimdron closed this as completed Mar 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants