npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ember-data-tasks

v1.1.1

Published

Task based (ember-concurrency) Ember Data API

Downloads

7

Readme

ember-data-tasks

An alternative Ember Data store that returns Ember Concurrency tasks instead of promises.

Install

ember install ember-data-tasks

This addon comes in three phases:

Phase 1: Store Override

By overriding the store with a mixin, we extend the behavior of methods on the store, like store.findRecord('post', 1).

Setup

Override your existing store, by creating a new store (or use your existing one, if you have it):

ember g service store

Open app/services/store.js and modify it to:

import DS from 'ember-data';
import TaskStoreMixin from 'ember-data-tasks/mixins/task-store';

export default DS.Store.extend(TaskStoreMixin);

Use

Now you can use your Ember Data store like before, and nothing has changed, since this store is backwards compatible, due to the fact that tasks also adhere to the promise spec.

But you didn't come here for the same old, you want immediate results. To take advantage of the benefits of tasks, you will have to wrap your store responses in a hash.

The example below will hit afterModel after the backend has resolved with data:

import Ember from 'ember';

export default Ember.Route.extend({
  model() {
    return this.store.findAll('post');
  }
});

But if you want immediate responses, do the following, and afterModel will be hit immediately:

import Ember from 'ember';

export default Ember.Route.extend({
  model() {
    return {
      postsTask: this.store.findAll('post')
    };
  }
});

Then you can utilize the task in your template like so:

<ul>
  {{#if model.postsTask.isRunning}}
    Loading your posts..
  {{else}}
    {{#each model.postsTask.value as |post|}}
      <li>{{post.name}}</li>
    {{/each}}
  {{/if}}
</ul>

This seems like a slight annoyance at first, due to the extra level of nesting, but in the end if you build ambitious apps, you will most likely return multiple tasks, and would have used Ember.RSVP.hash anyway, if working with promises.

Note: You can unwrap the task hash in setupController, if it really bothers you.

Phase 2: Model Override

This phase allows you to enable tasks for methods like model.save().

Setup

Open app/models/my-model.js and modify it to:

import DS from 'ember-data';
import TaskModelMixin from 'ember-data-tasks/mixins/task-model';

export default DS.Model.extend(TaskModelMixin, {
  // your model definition
});

You'd have to do this for every model, and if you have few, that should be easy. For those that have many models, you can do the following:

Reopen the DS.Model in your app/app.js file.

import Ember from 'ember';
import Resolver from './resolver';
import loadInitializers from 'ember-load-initializers';
import config from './config/environment';
// Add these two imports
import DS from 'ember-data';
import TaskModelMixin from 'ember-data-tasks/mixins/task-model';

let App;

Ember.MODEL_FACTORY_INJECTIONS = true;

App = Ember.Application.extend({
  modulePrefix: config.modulePrefix,
  podModulePrefix: config.podModulePrefix,
  Resolver
});

loadInitializers(App, config.modulePrefix);

// Add this model reopen
DS.Model.reopen(TaskModelMixin);

export default App;

Use

Now you can call model.reload(), model.save(), and model.destroyRecord() and get tasks back instead of promises.