An implementation of the Resource pattern in Ember.JS.
npm install ember-resources
# or
yarn add ember-resources
# or
ember install ember-resources
Or if you want to use main
(unstable) from git, you can use this in your package.json:
"ember-resources": "github:NullVoxPopuli/ember-resources#dist"
Which comes from this branch from this automation
See: API Documentation for more examples.
import { trackedFunction } from 'ember-resources/util/function';
class MyClass {
@tracked endpoint = 'starships';
data = trackedFunction(this, async () => {
let response = await fetch(`https://swapi.dev/api/${this.endpoint}`);
let json = await response.json();
return json.results;
});
get records() {
return this.data.value ?? [];
}
}
{{this.records}}
In this example, trackedFunction
will make a call to StarWars API
and if endpoint
changes from starships
to planets
, the trackedFunction
will
automatically re-call the StarWars API to fetch the planets.
Visit the docs on function-based resources.
This alternate API is more general-purpose, but has the same behavior as the above example.
import { resource, use } from 'ember-resources';
import { TrackedObject } from 'tracked-built-ins';
class MyClass {
@tracked endpoint = 'starships';
@use load = resource(({ on }) => {
let state = new TrackedObject({});
let controller = new AbortController();
on.cleanup(() => controller.abort());
fetch(`https://swapi.dev/api/${this.endpoint}`, { signal: controller.signal })
.then(response => response.json())
.then(data => {
state.value = data;
// ...
})
.catch(error => {
state.error = error;
// ...
});
return state;
});
}
{{#if this.load.value}}
...
{{else if this.load.error}}
{{this.load.error}}
{{/if}}
Resources [...] bridge a gap between imperative programming and declarative programming.
Ember templates are declarative. When we design a component [...] we are specifying declaratively the HTML that should be rendered. If the data used in the templates ever updates, then Ember will update the rendered output as well, and we don't have to worry about the details. We don't have to tell Ember which specific steps to take, and when - it figures everything out for us.
So.. what is a [[Resource]], really?
A Resource is a behavior that can be used in both templates and javascript.
A Resource is an alternate API for
import { cached } from '@glimmer/tracking';
import { SomeClass } from '../somewhere';
class A {
@cached
get myResource() {
return new SomeClass(this.args.foo)
}
}
In this example, myResource
returns an instance of a class and will re-create that
class if @foo
changes. That class can have its own internal state.
This requires at least 2 imports and 4 lines of code.
A Resource is a stateful helper:
{{#let (my-resource @foo) as |someClassInstance|}}
{{!-- ... --}}
{{/let}}
In this example, my-resource
returns an instance of a class and will re-create that
class if @foo
changes. That class can have its own internal state and is available
for use via the local variable myResource
.
This requires a stateful helper by globally available to your app. Helpers are typically stateless, so this would go against most guidance on helpers.
More information contained in the docs
folder.
High-fidelity sourcemaps are provided in the original typescript. However, you must be using embroider to take advantage of them. Sourcemaps should work with ember-auto-import@v2+ in non-embroider builds as well, but is untested.
Note, ember-resources is not guaranteed to be compatible with usage within @computed
getters.
Only auto-tracking is supported.
List of addons that use and wrap ember-resources
to provide more specific functionality:
See the Contributing guide for details.
This project is licensed under the MIT License.
This library wouldn't be possible without the work of:
So much appreciate for the work both you have put in to Resources <3
This is a V2-format Addon with V1 compatibility
Generated using TypeDoc