If I have a model with a relationship that contains something like this
it will cause one huge request which looks like
which will fail because the URI is too long. There should be an option to specify maximum length of URI and split this into multiple requests.
Here's a JSBin. It's not failing because apiary.io doesn't care about the URI length, but most servers will error if it's more than 255 characters.
I haven't personally tested it out, but #531 may solve this. Also related: #651
Closing as a duplicate of #651
@igorT I don't understand how #651 solves this issue? Also #531 was just closed without any fix... I'm currently trying to load a couple hundred IDs in my app and it'd be really sweet to be able to batch them. Much better than just not working at all.
@igorT Actually, soz... after having throught it through a bit more, I realise how having a separate link for groups of associated side-loaded values would/should solve this issue. :)
So there's a bug that causes links to not work for me (I think it's addressed/fixed by #1791)... which also means not having a pagination solution for #651 (which could be possibly dealt with by #1517) causes my app to just pretty much spit the 404 dummy (ie request malformed because of too many ids=?? values on the URL). Funtimes. I can realise the rationale behind #651 is good and everything, but it feels a bit like like it's a bug leaving ember ABLE to load more objects than can fit on a single URL request.