#emberjs

anyone have input on how to use slug for ember urls but still use id for backend lookup? http://discuss.emberjs.com/t/use-slug-for-page-...

from past attempt I where I set the backend up to accept both id or slug, I think an issue cropped up where ember would sometimes have 2 duplicate records where one was represented by id and one by slug

holler: there is no way

because ember has no way to map a slug to an id

is that a pretty common use case? feels like it would be

problem is I might have really long slugs in some cases.. doesnt seem ideal to use that as a db lookup

so somewhere it has to be mapped

have some mapping in your backend :P

hrmrm damn

if it's indexed I don't see why the size would matter that much

I wonder if there is a way to use id but somehow change the location hash

immediately

no

I guess that is issue though on refresh

yup

rawr

ok so I will need to use slugs throughout I guess

dont see any other way around that

yup

will see where I get.. thx

hey guys. i'm using ember-cli, i've set locationType as hash in environment.js, yet when i try to access a server resource directly in the address bar without using a hash before the url path, it seems ember is still loading. i have my api on the same host/port as the ember app atm.

i have an api endpoint that returns images based on an id. if i embed an <img> in a template with a url such as http://localhost:4200/api/image/234, the image is displayed. but when i open up a new window and set that same address, the ember app loads instead of the image.

btw, i've set ember-cli proxy to an asp.net webapi running on a different port than 4200

rhyek: are you using the proxy option?

alexspeller: yes

rhyek: sounds like a content type issue - your browser will request html not an image because there is no extension in that url

i suppose you're right. when loading the index of images, where i have <img> tags, those requests are being sent with Accept: "image/png,image/*;q=0.8,*/*;q=0.5"

rhyek: the ember cli proxy behaviour is not that advanced

rhyek: how will you be serving your api in production?

well, currently i'm still in heavy development even though the app is already running in production. atm i'm running ember-cli on the production server until i figure out a better way

rhyek: oh, you shouldn't be doing that