Why is this an issue?

Sharing some naming conventions is a key point to make it possible for a team to efficiently collaborate. This rule allows to check that all package names match a provided regular expression.

How to fix it

Code examples

Noncompliant code example

With default regular expression ^[A-Z]|[A-Z]+[A-Za-z0-9]*[A-Za-z0-9]+$:

package provide fly 1.0.0

Compliant solution

With default regular expression ^[A-Z]|[A-Z]+[A-Za-z0-9]*[A-Za-z0-9]+$:

package provide Fly 1.0.0

Known limitations

The rule is not checked if the name of the package is dynamic:

package provide $my_variable 1.0.0