ember always thinks in terms of IDs so we need to work out a good pattern for avoiding this.

e.g.
* [routes expect params](https://github.com/balanced/balanced-dashboard/blob/master/app/routes/router.js#L8)
* [they then pass these params to the models](https://github.com/balanced/balanced-dashboard/blob/master/app/routes/marketplace.js#L3)

For fetching related resources there's no issues since we have the original URI from the parent object but fetching that parent object is the tricky part. In the original dashboard I always just used `window.location.path` to find this but I as we move to root level resources this is only going to get harder to do since we need the URL of the page to carry some context information such as marketplace since we need to know marketplace in order to know which key we are going to make requests with. 

I don't expect this to get any better until we have oAuth so we can use a single key for requests across many resources.

In closing however, you're right and wrong, using this for most things is a code smell, but to find the marketplace's URI we either do this or parse the URI from the URL.