REST conventions for single tree stores.
npm install resting-ducks --save
import { Duck, Api} from 'resting-ducks'
const client = new Api({host: 'http://localhost:8000', resource: 'tasks'})
const tasks = Duck(client, {})('myTasks')
const store = createStore(tasks.reducer)
store.dispatch(
task.create({id: 10, name: 'Clean the windows', resolved: false})
).then(() => {
task.update({resolved: true}, 10, {patch: true})
})
The state is stored using immutable.js
The constructor accepts two arguments:
client
an API to interact with your server. You can use the one provided by default inresting-ducks
wich uses fetch-please for promise and canceleable requests.options
indexes
An array of attributes you would like your model indexed by. Defaults to['id']
import { Duck, Api} from 'resting-ducks'
const client = new Api({host: 'http://localhost:8000', resource: 'tasks'})
const tasks = Duck(client, {
indexes: ['id', 'project_id']
})('myTasks')
const store = createStore(tasks.reducer)
Defines how you interact with your server.
Must implement fetch
, post
, put
, and del
.
Options:
host
Mandatory. The host of your serverresource
Mandatory. The name of your resourcebase
Defaults to/
. The prefix (for instance versioning) of your API
import { Api } from 'resting-ducks'
const client = new Api({
host: 'http://localhost:3000',
resource: 'users',
base: '/v2'
})
const {xhr, promise} = client.fetch()
promise.then((data) => {
console.log(data)
})
// Timeout of 500ms
setTimeout(() => {
xhr.abort()
}, 500)
Resting ducks come with all the common REST actions so you don't have to re-implement them over and over in your stores.
The reducer for your resource. Add this one to your store and you are all set!
Replace the current resources with the given ones.
If a id
/cid
is given, it applies only to the given resource
Patch the resource with the given attributes.
Marks the current duck as having an ongoing cancelable request. You can use this to represent a loading transaction and cancel it if needed.
If a id
/cid
is given, it applies only to the given resource
Marks the current duck as having an error. You can use this to represent it.
If a id
/cid
is given, it applies only to the given resource.
Append a new resource on the duck.
Remove a resource.
Retrieve your models from your server.
It marks the request
object so you can track progress and cancel
it if needed.
In case of error it marks the error
object.
Send a new resource to your server. The new resource is optimistically added on the client.
It marks the request
object so you can track progress and cancel
it if needed.
In case of error it marks the error
object.
Send new attributes for your resource to your server. The new attributes are optimistically set on the client.
It marks the request
object so you can track progress and cancel
it if needed.
In case of error it marks the error
object.
Extra options:
patch
: Wether the attributes are a patch or a full representation of the resource. Defaults to false.
TODO
Add support for PATCH
Destroy a resource on your server. The resource is optimistically removed on the client.
It marks the request
object so you can track progress and cancel
it if needed.
In case of error it marks the error
object.
create
, update
and destroy
are optimistic by default. You can
disable that behaviour passing the optimistic
flag to false
.
Your tree will have the following schema:
resources: [
{ // Information at the resource level
cid: String, // Client side id. Used for optimistic updates
request: { // An ongoing request
label: String, // Examples: 'updating', 'creating', 'fetching', 'destroying' ...
xhr: Object, // The xhr object. You can abort it with `xhr.abort()`
},
error: { // A failed request
label: String, // Examples: 'updating', 'creating', 'fetching', 'destroying' ...
error: String, // A string representing the error
},
attributes: Object // The resource attributes
}
] // Information at the collection level
cid: String, // The latest Client id generated
request: { // An ongoing request
label: String, // Examples: 'updating', 'creating', 'fetching', 'destroying' ...
xhr: Object, // The xhr object. You can abort it with `xhr.abort()`
},
error: { // A failed request
label: String, // Examples: 'updating', 'creating', 'fetching', 'destroying' ...
error: Object, // A string representing the error
}
(The MIT License)
Copyright (c) 2016 Pau Ramon masylum@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.