Issues with customized before/after use of Delimiters

[nancyrisch]

When I've configured a component to only use the delimiter either before or after, and then also customized which components are used within a naming, delimiters are added in an inconsistent manner.

In my scenario, the order of components is:
Org - Units/Depts - Location - Function - Environment - Project - Instance - Type.

I've customized delimiters on Location (only use after), Function (only use before), and Instance (only use after). So, the delimiter pattern would be:
-ORG- -UNITS- LOCATION- -FUNCTION -ENVIRONMENT- -PROJECT- INSTANCE- -TYPE

When I build a resource name using only the UNIT, LOCATION, FUNCTION, ENVIRONMENT, INSTANCE (the ORG, PROJECT, & TYPE components are excluded) I get the expected result:
UNITSLOCATION-FUNCTIONENVIRONMENTINSTANCE

However, I build a resource that uses ORG, UNITS, LOCATION, ENVIRONMENT, PROJECT, TYPE (the FUNCTION & INSTANCE components are excluded) the expected results are:
ORG-UNITSLOCATION-ENVIRONMENT-PROJECT-TYPE

Actual results are ORG-UNITSLOCATIONENVIRONMENT-PROJECT-TYPE

Why is the delimiter skipped between LOCATION and ENVIRONMENT when the delimiter use is configured to follow LOCATION and precede ENVIRONMENT.

It appears that in order for the delimiter to be included it must be configured to follow the first component AND precede the second component. If either of those delimiters is disabled, no delimiter would be added, but when a component is excluded, that delimiter logic does not seem to hold.

Has anyone else used the delimiter setting on the components to disable when the delimiter is used (before/after) the component?