Open
Description
Consider the following use case:
group("signing") {
group("pgp") {
enumeration("enabled") {
defaultValue.set("AUTO")
values.addAll("AUTO", "OFF")
description.set("Configures whether PGP signing should be enabled or not. By default (AUTO) signing is enabled for release versions")
}
enumeration("implementation") {
defaultValue.set("IN_MEMORY")
values.addAll("IN_MEMORY", "GPG_CLI")
description.set("Configures PGP implementation to use. By default (IN_MEMORY) PGP keys are stored in memory")
}
}
group("sigstore") {
enumeration("enabled") {
defaultValue.set("AUTO")
values.addAll("AUTO", "OFF")
description.set("Configures whether Sigstore signing should be enabled or not. By default (AUTO) signing is enabled for release versions")
}
}
}
enabled
generates the following:
package buildparameters.signing.pgp;
public enum Enabled {
I am afraid Enabled
would collide between .sigstore.Enabled
and .pgp.Enabled
, and I would like to make enum names a bit more specific.
For instance enum PgpEnabled
vs enum SigstoreEnabled
.
Metadata
Metadata
Assignees
Labels
No labels