ReleaseNotes_0_2_0

Release Notes for n-odata-server

Version 0.2.0

Generated on 2015-11-25

Items included in this release

Implement service document request

Implemented. When service is called via .../odata/ the service document is returned

Implement Delete requests (DELETE)

Implemented deletion of entity by id

Implement Update request (PATCH, MERGE)

Implemented functionality

Implement provisioning as npm package

Project is available now on npmjs.org

Implement basic Query requests (GET)

Implementation finished

Implement $top option for GET requests

Functionality is implemented

Implement $skip option for GET requests

Functionality is implemented

Implement $count option for GET requests

functionality implemented. If $count parameter is defined the query only returns the number of records for the defined collection / entityset

Implement server-driven paging

Implemented functionality. The config parameter can be set as option parameter in component-config.js of the server application. E.g.

  "n-odata-server": {
    "path": "/odata/*",
		"maxpagesize": "2"
  }

The default value for this parameter (if not specified) is 1000. This parameter can also be given via the URL request header odata.maxpagesize' so it might look like Prefer odata.maxpagesize=50`

Enable customizing of odata prefix in URL

Implementation finished. The server application can define the prefix now in server/component-config.json. The example above can be realized like following:

  "n-odata-server": {
    "path": "/myservice/*",
		"maxpagesize": "200"
  }

Return OData-Version in response header

Function is implemented. I created a BaseRequestHandler class in which I implemented the function setODataVersion. From this base class the get-, post-, put- and delete-handler classes inherit and they call the new function when handling a request.

Implement $select option for GET requests

The parameter is evaluated when a collection or a single entity request is send by the client. It is implemented in odata_get.js/_applySelect