it might be because adapters get a snapshop instead of the actual record
loglaunch
i just read that
ive also noticed that nested data doesnt get updated after it is retrieved from the server
only if it is already cached
maybe the adapter needs work
ill look into it
locks
ping mixonic
loglaunch
who is that?
locks
major embereƱo
cibernox joined the channel
and he has commits on that adapter
nathanpalmer joined the channel
gmurphey joined the channel
shama joined the channel
viki_ joined the channel
madnificent joined the channel
axsuul has quit
iamolivinius joined the channel
nathanpalmer has quit
samselikoff joined the channel
Methodical joined the channel
tyleri has quit
Methodical has quit
axsuul joined the channel
seanouimet has quit
H1D_ has quit
jonr22 joined the channel
H1D joined the channel
davidconnolly joined the channel
seanouimet joined the channel
mobe has quit
Kerry350 joined the channel
slemgrim has quit
iamolivinius has quit
Salen joined the channel
robpark joined the channel
jonr22 has quit
iamolivinius joined the channel
rando joined the channel
peterwagenet
locks, mobe: I don't think 2.0 will be the next one after 1.11
just a heads up
might be a couple more cycles
kurko_ has quit
we're planning to set a date soon
because there's always more we *could* do :)
gotta draw a line
locks
roger
sandstrom has quit
half a year ago 1.10 was going to be the last one before 2.0 ;P
jlle joined the channel
peterwagenet
hmm, guess mobe is gone
sandstrom joined the channel
locks: yeah, always takes longer than you hope :)
but we've got a lot done
and we'll be setting ourselves a deadline soon
Kerry350_ joined the channel
locks
yeah, all of the htmlbars work was massive
peterwagenet
don't want to rush it, but also don't want to delay unless absolutely necessary
locks
and I guess 2.0 needs to happen at the same time as ED 1.0 and CLI 1.0?
"needs"
iamolivinius has quit
peterwagenet
locks: not sure
and the goal is still a smooth upgrade path to 2.0
I think we're hoping to write some guides on future proofing your apps
pzu has quit
but at the very least, just hop the way up each release and fix the deprecation warnings
locks
I can lend a hand
darpa1 joined the channel
darpa1 has left the channel
someone wrote a blog post on the subject
iamolivinius joined the channel
and there's a presentation too
hyejinkim joined the channel
peterwagenet
cool
talk to trek if you can get a hold of him
maybe tweet at him
there's work on new guides around ember-cli
locks
I'm already in the CLI rewrite team thingie
peterwagenet
ah good
I forgot that
I lose track of people :P
anyway, gotta go
heading to the airport soon
locks
there's a lot of people
have a safe trip o/
peterwagenet
the more the merrier
thanks :)
sandstrom has quit
thejchap has quit
codeurge joined the channel
migbar has quit
iamolivinius has quit
joshsmith has quit
migbar joined the channel
honzahovorka joined the channel
codeurge has quit
iamolivinius joined the channel
jbinto joined the channel
iamolivinius has quit
migbar has quit
honzahovorka has quit
lov2cod joined the channel
bkaney joined the channel
iamolivinius joined the channel
slemgrim joined the channel
edude03 has quit
slemgrim has quit
iamolivinius has quit
sandstrom joined the channel
Utropics
Hi All -- if i'm using ember data and i want to query my api and retrieve several items if their id's match an array of ids, what would be the syntax for that?
hyperlink has quit
migbar joined the channel
hyperlink joined the channel
NickChri_ joined the channel
teufelChiCoder joined the channel
locks
Utropics: store.find('modelName', { ids: [1,2,3,4] }); and it's serialize to a query param, like /modelName?ids=[1,2,3,4]
(or whatever the syntax is)
__kane__ has quit
cibernox joined the channel
NickChristensen has quit
einarj joined the channel
Utropics
locks: If i have to override the query param serialization, where would i do it? right now i have coalesceFindRequests turned on in my adapter and I overwrite the entire findMany method
aroberts has quit
i would prefer to do it in a more generalized fashion, but i don't know that buildURL is the right place to do it