Required and optional scope-enum

Expected Behavior

Hello everyone and thanks for your hard work! I recently faced a use-case and I’m not sure if my idea is achievable with the current implementation.

I’m working on a no-managed legacy mono-repo where every single folder is a project.

I would really like to set some rules that somehow enforce:

• no empty scopes in order to always have in the git history the reference to the edited project (scope-empty) ✅
• set the possible scopes (scope-enum which already supports multiple scopes) ✅
• set which one is required and which one is not (e.g I may want to highlight in the scope the project but also what has been done feat(project-a, docs): .... It would be also ok to just specify the project as scope feat(project-a): ..., but feat(docs): ... should not be valid) 🤔

Current Behavior

"rules": {
      "scope-empty": [2, "never"],
      "scope-enum": [2, "always", [
        "project-a",
        "project-b",
        "api",
        "docs",
        ...,
        ]
      ]
    }

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

"rules": {
      "scope-empty": [2, "never"],
      "scope-enum": [2, "always", [
        "project-a",
        "project-b",
        "api",
        "docs"
        ]
      ],
      // No more than one of...
      "scope-required-enum": [2, "always", [
        "project-a",
        "project-b"
        ]
      ],
      "scope-optional-enum": [1, "always", [
        "api",
        "docs"
        ]
      ]
    }

Does it makes sense to you? Would it be probably better to create a plugin like selective-scope

[andreafspeziale]

I think my use-case is very specific so I will leave my solution here just here for the moment. Thanks for the help in the meanwhile! Stay safe!

[escapedcat]

Only a suggestion if you want to do that.