I vote that this separator is not moved into a common module. We should try to stop leaking things out of “modules”. The only reason why we have a requirement on the “/“ is to symbolize contextualization. I assume this came about because of sub-regions.
I think we should rather aim to improve this behavior, by assuming that Regions are on “root” level. That means “/RegionName” should be expressed as “RegionName”. I think that the dependency on “/“ in the Region name is something that we should remove. But for now, not to make this worse, let's not add this constant into places where it does not belong. As @Anil stated, it should not be visible, so let’s not make it visible. Let’s rather fix the API’s to not require this contextual, syntactical sugar that we have forced onto a name. But in the meantime, we can have a private constant in the management module. —Udo On May 18, 2020, 12:25 PM -0700, Jacob Barrett <jbarr...@pivotal.io>, wrote: On May 18, 2020, at 10:15 AM, Udo Kohlmeyer <u...@vmware.com> wrote: I was wondering. Why do we require to add this Region.SEPERATOR to be anywhere outside of Region. Geode-management was purposefully designed NOT to have a dependency on core. Creating a new dependency on a donor module, just means that management module will now start knowing about geode. The proposal was updated to move the separator to common not core. Module geode-management already has a dependency on geode-common.
