1.2.1 • Published 5 years ago

hyresources v1.2.1

Weekly downloads
Last release
5 years ago


hyResources is a restful resource manager. it helps you configure resources and store them in one module. hyResources (HeiYuki Ressources) is very simple to use

Get hyResources

We recommend downloading this package with a dependency manager beceause it has a dependency with angular and angular-resource. if you just download this package then you should also get angular and angular-resource: https://github.com/angular/bower-angular https://github.com/angular/bower-angular-resource

How to start

You should use the included file in 'dist/hyResources.min.js'

or build it:

# download the project
git clone https://github.com/heiyukidev/hyResources.git
cd hyResources/

#install with npm
npm install hyresources

#install with bower
bower install hyResources

# install yarn ( as administrator )
npm install -g yarn

# install seed dependencies


To get the module to work you of corse need to import it in your HTML file. Since hyResources relies on ngResource you also need to import angular-resource.js with hyResources.js

<script src="angular/angular.min.js"></script>
<script src="angular-resource/angular-resource.min.js"></script>
<script src="hyResources/hyResources.min.js"></script>

hyResources is an AngularJs module that you first need to inject:


How to Use

hyResources Offers a service named : 'hyResources'. This service will handle all your restful resources by storing them inside the localStorage of the client's machine.

Adding resources

To add a new resource to the storage simply:


you can assign your resource a significant name for better visibility.

you can of corse add multiple resources at the same time.


The best way to handle this is to run a function during the configuration phase that adds the resource that your module is requiring and to edit all the configuration once (see below for configuration).

Note: you only need to add a resource once!

GET request

To perform a get request to a specific resource you use:

           //Callback Logic

to perform a get request to a specific resource with a parameter you simply use:

           //Callback Logic

POST request

to perform a post request to a specific resource :

           //Callback Logic

data is the body of the request the callback function is not necessary. you can just call:


PUT/DELETE request

to perform a put/delete request to a specific resource :

//PUT Request
           //Update Callback Logic

//DELETE Request
           //Delete Callback Logic

data is the body of the request the callback function is not necessary. you can just call:

//PUT Request
//DELETE Request


Note: hyResources will send the request to the API's url + the data "id" field (you can change the id field to correspond with your object's id, see below)

    //Other data fields

Then your request will be sent to : https://exemple.com/posts/4

if your data doesn't have an id field the request will be sent to : https://exemple.com/posts

Customize Resources

Changing URL

You can Change the URL of a resource any time you want to by executing the folowing command


Note: if you change the URL it will change for all future requests

Customize Headers

You can add different headers to each of the methods pre-defined in hyResources. You need to access the Method first via the method function then specifie the header you want to add.


Method names are the names mentionned earlier in the Requests Section: get, add, update, delete.


isArray is a boolean that indicates if your restfull API returns an Array or an Object. by default it's false except for the get method.

Note: using the get Method with a parameter has it's isArray value to false and is not editable. To get around this you can constantly change your URL before a request, a fix for this is Upcoming

to change the value of is array, you have to access the function via the method function then set the new value to isArray. you only need to do this once preferably after you add the resource with addResource.



According to restfull APIs standards, the GET,PUT and DELETE methods requests a parametred URL with the id of the object.By default, hyResources looks for an id value in the object you're interacting with. If you use a diffrent value name to identifie your object you can specifie it using this method. you only need to do this once preferably after you add the resource with addResource.


Advanced Config

you can set up the resource on your own by using the following structure:

            "GetParams": { //Parameters for the get function of the resource
                "headers": {
                    "Accept": "application/json",//These are examples
                    "Authorization": "TOKEN"
                "Method": "GET",
                "IsArray": true
            "AddParams": { //Parameters for the add function of the resource
                "headers": {
                    "Content-Type": "application/json"
                "Method": "POST",
                "IsArray": false
            "UpdateParams": { //Parameters for the update function of the resource
                "headers": {
                    "Content-Type": "application/json"
                "Method": "PUT",
                "IsArray": false
            "DeleteParams": { //Parameters for the delete function of the resource
                "headers": {
                    "Content-Type": "application/json"
                "Method": "DELETE",
                "IsArray": false
            "extra": {
                "defaultId": "id"

Note: you can change the HTTP Methods to anything like PATCH, OPTION, or even have the get function send a PUT request. You can also have multiple headers like in the exemples


to Implement the configuration you structured you simply call

//config is the json objec former earlier

Dev Tools

A couple of small functions that will help you understand how this resource works by seeing how it stores data under the hood.

//Logs all the resources registered at the moment the function is called
//Logs a Single resource
//Returns an object that represents how data is structured inside the module