You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calculation quite arbitrarily counts numbers of wildcards. I feel that also the wildcard's position should be taken into account as well. For example com.foo.bar.**.abc.de feels more specific than com.foo.**.bar.abc.de.
In general, if a pattern is a prefix of another, the pattern where the first wildcard occurs later (farther right) is more specific than the other
The text was updated successfully, but these errors were encountered:
From version 2.x.x on, specificy will be defined as follows:
A single part of a pattern can be assigned a specificy like this:
Part
Specificy
**
0
*
1
else
2
When comparing 2 patterns for specificy, we simply calculate the specificy of the first part, in which both patterns differ. If no such part exists (= one pattern is an exact prefix of the other), the specifixy is calculated by comparing both pattern's part count. So naturally the longer pattern becomes the more specific one.
Calculation quite arbitrarily counts numbers of wildcards. I feel that also the wildcard's position should be taken into account as well. For example
com.foo.bar.**.abc.de
feels more specific thancom.foo.**.bar.abc.de
.In general, if a pattern is a prefix of another, the pattern where the first wildcard occurs later (farther right) is more specific than the other
The text was updated successfully, but these errors were encountered: