Add a slugged endpoint for users/organizations about deprecated-code-corps-rails-api

[joshsmith]

We'll also likely need a matcher for /:slug/:project_slug

[joshsmith]

Also see this for more explication: http://stackoverflow.com/questions/33837394/rails-same-top-level-url-route-for-organizations-user-domain-com-user-and-domai

[begedin]

The rails side seems relatively simple.

The ember side would be the complicated one, but I guess we could do a manual ajax request instead of a store.find, followed by figuring out if we got back a user or an organization, pushing it to the store and then and then either redirect to the proper route, or just set the controller model , the type of which determines if we render an organization or a user component. I'm not really sure which one is better in this case, but redirecting to a route would add the additional difficulty of making sure our URL is in the format we'd like it to be.

My question for the rails side is, how would we want to handle our slug?

Is it just a parametrized username/organization.name? Can it be editable? Do we use a gem, such as friendly_id, or just make a slug field and use find_by_slug? From what I remember from other projects, when we were using a the friendly id gem, there were some complications we had to deal with, both on the API and Ember side.

If we decide in advance the API will never allow us to fetch a user or an organization by id directly, it might be easier to not use the gem and just add a slug field and always fetch by it.