Clean up the way exported global values are defined.

[peterp]

No description provided.

[thedavidprice]

@peterp Ah, this one seems important and I know globals have come up in the forums a few times. So I want to make sure I grok it accurately and will include in the release notes.

And I wonder where/if we should document globals -- seems like we only have two right now: apiProxy and Auth. Thoughts?

Original Code:
Created a Global __REDWOOD__, and other values were attached to it, e.g. API_PROXY_PATH.

New Code:
Eliminates __REDWOOD__ and uses window global instead for attaching values.

Renames API_PROXY_PATH to __REDWOOD__API_PROXY_PATH, which is now attached to window.

---

edit: hmm, I'm working on a doc with Dom and just realized if people have been using __REDWOOD__ to access config values this might be a breaking change, correct?

[jtoar]

@thedavidprice @peterp I was using this discussion on the forum as my source: https://community.redwoodjs.com/t/getting-cors-error-while-calling-a-lambda-function/186/6.

[peterp]

@thedavidprice @jtoar I don't think we should document them, since I consider them an "invisible implementation detail" and should not be surfaced to users.

__REDWOOD__ is a safe space for us, but if people wander off the golden path and want the apiProxyPath we should create a proper way for them to get those configuration options in the web side.