Updated host to look for empty string in hostname instead of host

[donaldpcook]

For #60. This change shouldn't matter, as it resolves to window.location.hostname regardless, but changed it from window.location.host to window.location.hostname for consistency's sake.

[bmuenzenmeyer]

Hi @donaldpcook can you please change this to merge with the dev branch? If you don't I will change this manually this weekend and close PR.

[donaldpcook]

New pull request #71 with this merged into dev.

[ebednarz]

"This change shouldn't matter, as it resolves to window.location.hostname regardless"

Huh? window.location.host includes the port unless it is the default port for the protocol, and that seems to be exactly what the commit message says. Many (I'd hope most) developers won't run a local server on a port lower than 1024.

[donaldpcook]

@ebednarz you can check the commit. The file always saved window.location.hostname to host. It used to check if window.location.host was an empty string. Now it checks if window.location.hostname is an empty string. It shouldn't matter in that if window.location.hostname is or isn't empty, window.location.host is also going to or not going to be empty.

[ebednarz]

@donaldpcook we might have a minor disagreement about 'always' here :-)
My issue is from 09-16, I now see there is a commit that assigns the locations hostname instead of host property from 09-24: bab8e8c
Your comment was the first notification I got, and missing the above change I admittedly misunderstood what you meant by 'resolves to'.

[bmuenzenmeyer]

Without looking too far into the past, I suspect my original commit was a typo from a manually-merged PR against master.

Thanks for the discussion and continued interest in patternlab-node!

[donaldpcook]

That explains it @ebednarz!

Thanks!