Improve config option metadata to define where options can be used and improve JSON schema #26571
Labels
core:config
Related to config capabilities and presets
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
type:feature
Feature (new functionality)
Describe the proposed change(s).
Enhance this source file: https://github.com/renovatebot/renovate/blob/main/lib/config/options/index.ts
Right now we have some options with "parent" defined (such as
packageRules>matchPackageNames
) but it's not enough info to generate the JSON schema accurately when options such asenabled
can be at root or withinpackageRules
, or options such asconfigMigration
must be at the root of config.It's even more complicated when you consider that we support some dynamic config options such as
minor
, or manager names such asgomod
.We should brainstorm about all the possible objects which config can be in (root, hostRules, packageRules, managers, etc) and then define the syntax. Perhaps
parent
should just be an array instead of single string.The text was updated successfully, but these errors were encountered: