I think I can make a case for allowing this separator to be hardcoded in unit tests; if the separator changes, these tests will fail, and we will know immediately. Having to use the `getSeperator` method everywhere is only slightly more convenient than having to build a list by hand.

Obviously it is NOT ok to hardcode this separator in the "main" codebase.

Lets discuss in the standup later.