blowdryerInline
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- groovy, kotlin
- Domain
- build-system, cli
Research direction
Start by locating the existing handling for blowdryer.file() and the Gradle plugin entry point behind gradlew tasks. Done means a blowdryerInline task can recursively expand referenced files into temporary .blowdryer-inline.gradle files and optionally restrict processing with --file.
Written by the indexing model from the issue text.
Description
After using blowdryer for a bit, it's made our build files much easier to read, since all of our common patterns have been refactored into one repository and it's only the high-entropy stuff that's left to view. My biggest worry is that other people will have a hard time reading them, since they are now obfuscated a bit.
Here is a proposed enhancement. It's fine to implement only for groovy or only for kotlin - people who want the other would benefit hugely from the existing as a guide.
Viewing a blowdryer-enhanced project
If you are working with a project that uses blowdryer, especially someone else's project, it can be confusing to track down the build scripts they are calling out to. To address this, you can use gradlew blowdryerInline and it will do the following:
- for every gradle file (
foo.gradle) which usesblowdryer.file() - write out a new temp gradle file (
foo.blowdryer-inline.gradle) - where each call to
blowdryer.file()has been recursively copy-pasted into the expanded file for easy viewing
You can limit this to just one file with gradlew blowdryerInline --file someFile.gradle
- Dominant language
- Java
- Stars
- 29
- Forks
- 6
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from diffplug/blowdryer
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement pr-welcome
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
enhancement pr-welcome
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in diffplug/blowdryer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
HL7/fhir-ig-publisher#1375 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Flaky: a relaunched catch-up replay can still report catching up right after its marker is written Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
johanhaleby/occurrent#1134 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/jeo-maven-plugin#1811 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100