Meta artifact containing all the splits
See original GitHub issueI’m aware that the whole point of this library is that you use the modules you need to keep apk size down. The thing is, when using lots of the splitties like I do in several projects it would be more convenient to be able do add one meta dependency containing all splits. Cleans up the build.gradle and with Proguard/R8 everything thats not used it thrown out for release builds anyway.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Current and Novel Techniques for Metal Artifact Reduction at CT
(c) Diagram shows a single-source CT scanner with a split filter at the output of the x-ray tube, which splits the x-ray beam...
Read more >Methods to address metal artifacts in post-processed CT images
The software then 'splits' the image into two split parts. One split part contains the fractured vertebra and other vertebrae distal to it,...
Read more >Nonlinearly scaled prior image‐controlled frequency split for high ...
Abstract Purpose This paper introduces a new approach for the dedicated reduction of high-frequency metal artifacts, which applies a nonlinear scaling (NLS) ...
Read more >“Frequency split metal artifact reduction (FSMAR) in computed ...
The paper I have chosen for critical review is “Frequency split metal artifact reduction (FSMAR) in computed tomography” by Meyer et al., published...
Read more >Methods of Meta-Analysis: Correcting Error and Bias in ...
Meta -Analysis of Correlations using Artifact Distributions ... Indeed, this may be the case for all artifacts other than sampling error.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Here are all the groups I plan to have:
Notably absents are:
alertdialog(to avoid confusion in IDE autocomplete if also using alertdialog-appcompat)arch-lifecycle(I’d like to split it up and removed overlap with AndroidX KTX artifacts in the future)arch-room(because I use SQLDelight instead of Room for databases, and not all apps need Room)checkedlazy(I’m not sure it’d be helpful to everyone, so I think it’s better to keep it separate)exceptions(same as for checkedlazy)initprovider(same as for checkedlazy)lifecycle-coroutines(because it will overlap with AndroidX Lifecycle KTX and with upcoming fix in R8 then D8 for https://github.com/Kotlin/kotlinx.coroutines/issues/878)stetho-init(because should only be used for debug builds, or a subset of those, for those who want to use it)typesaferecyclerview(same as for checkedlazy)views-dsl-ide-preview(same as for stetho-init)I’m still not decided on the base name (prefix) of those artifacts. If you have any ideas, please tell me, it can be helpful.
Version 3.0.0-alpha05 should be available tomorrow in the day with docs for the grouping artifacts, and for the new permissions split.
All this is already available in the latest dev version (
3.0.0-dev-008see instructions in README on the develop branch). I need to write the changelog before releasing properly, but I also need to sleep.