Resolve Type.getList promise outside can-connect behavior scope


#1

Hi,
Knowing that “getList” implementation at can-connect/constructor actively resolves the getListData() promise how can I take control of the promise Type.getList resolution in my client code without completely break the getList flow (getListData -> hydrateList -> …) ?

Thanks!


#2

As @nlundquist point out in gitter the easiest workaround would be to wrap the Model.getList() promise in a executable function.