Configuration Documentation should be project specific
Open
weekly-action-item
- Dominant language
- Groovy
- Stars
- 2.9k
- Forks
- 975
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 92
Description
### Issue description
https://github.com/apache/grails-core/pull/15721 identified configuration metadata existing only in grails-core, we need to split the configuration values so they're defined in the project that uses them.
Contributor guide
Research direction
Start by reading the issue and Apache Grails PR 15721, then locate where configuration metadata currently exists only in grails-core. Identify the projects that use those configuration values and verify how their metadata is documented. Done means each value is defined in the project that uses it rather than centrally in grails-core.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100