node-gradle / node-gradle/gradle-node-plugin
FAQ suggests getEnv instead of gradle provider
Open
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 677
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
this is a snippet of kotlin dsl I'm using for another plugin, I'm not sure on the groovy syntax, but this is how you should get a property. Sadly I don't fully understand it, but apparently, this is better.
val isCI = providers.environmentVariable("CI").forUseAtConfigurationTime().isPresent
ratchetFrom = if (isCI) "HEAD~1" else "HEAD"
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Locate the FAQ entry that currently suggests getEnv and review the Gradle provider example in the issue. Update the guidance with the appropriate provider-based approach and Groovy syntax, then verify that the FAQ no longer recommends getEnv.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, kotlin
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100