enginustun / rest-in-model Goto Github PK

It causes a confusion and it should be provided in same way for both.

We should add request timeout to settings.

maybe add to x-www-form-urlencoded setting for oauth operations

We should improve model and config definitions as below:

export default class Foo extends RestBaseModel {
  getConfig() {
    return {
      headers: {},
      // idField: 'id',  #deprecated
      resultListField: 'result',
      paths: { default: 'foos/', byQuxId: 'foos/{quxId}' },
      endpointName: 'gateway',

      fields: {
        // idField definition deprecated, use primary attribute instead.
        id: { primary: true },
        bar: { default: 'baz' },
      },
    };
  }
}

Use following lines:
[![npm version](https://badge.fury.io/js/office-ui-fabric-react.svg)](https://badge.fury.io/js/office-ui-fabric-react) [![Build Status](https://travis-ci.org/OfficeDev/office-ui-fabric-react.svg?branch=master)](https://travis-ci.org/OfficeDev/office-ui-fabric-react)
And output like that below:

Like that alarmDevice:

We can add mock data support. Add mock data to model folder and decide source by a setting attribute.

Currently, we are able to specify 'resultListField' in parameter while calling function.
DerivedModelClass.all({ resultList:[], resultListField: 'content' });

If we update code as below:

We will be able to define resultListField in model class.

const restModelToObject = (restModel, Type) => {
  const newObject = new Type();
  const config = Type[`${Type.name}_config`];
  if (helper.isObject(config.fields)) {
    const fieldKeys = Object.keys(config.fields);
    for (let i = 0; i < fieldKeys.length; i += 1) {
      const fieldKey = fieldKeys[i];
      newObject[fieldKey] = restModel[config.fields[fieldKey].map || fieldKey];
    }
  }
  return newObject;
};

This assignment overrides default value of newObject. It should check if given model's current attribute is undefined then do not assign this attribute of newObject.

Supported end point only accepts array to update multiple records at once. It could be nice to have such support with something like this :

const somethingModelArray = [
  {
    something: 'something1',
    anotherThing: 'anotherThing1',
  },
  {
    something: 'something2',
    anotherThing: 'anotherThing2',
  },
];
const somethingModelArrayInstance = new SomethingModel(somethingModelArray);
somethingModelArrayInstance.save({ modelArray: true });

Maybe we will add xhr file upload property.

I want type code like following