Enable a default delimiter for parsing behaviour

[blakeembrey]

@DylanPiercey - this might help you with handling hostnames. Let me know 😄

[DylanPiercey]

@blakeembrey looks sweet to me, thanks for looking into working with hostnames.

Currently the lib works fine for me with hostnames and I am having a little trouble following exactly whats changed in terms of functionality. Could you elaborate what this commit has fixed or changed at a high level?

[blakeembrey]

Yes, sorry. I enabled delimiter to be passed in as a parse option. Before it assumed the default delimiter to always be /. The only place this would come up is in :foo+.com or :foo*.com where it'd assume a/b/c instead of a.b.c because of the default delimiter character.

[coveralls]

Coverage increased (+0.004%) to 99.363% when pulling 7b351aa on default-delimiter into 9932d18 on master.

[DylanPiercey]

Ah cool, thats sweet. I saw the delimiter option but wasn't exactly sure what it was doing.

I have never personally had a situation where I wanted one or more domains in a group but this is sweet functionality to add and will definitely help people (like me) who might have guessed that would work before :p.

Would love to see this merged so I can update Rill :D.

Thanks for your work!

[coveralls]

Coverage increased (+0.004%) to 99.363% when pulling c9a4c67 on default-delimiter into 9932d18 on master.