Find all notable changes of this project in this file.
- update library to be compatible with
ra-core 4.1.5
- required re-release as I missed to transpile all and upload the features of 1.1.7 to npm.
- fixed bad behaivor with compound keys while using field named
idissue #27 and issue #19 - @kenfehling
- #26, added rpc filter support, which is explained here - @TheRealAstroboy
- #24, fixed eq. prefix for non-compound keys issue #23 - @andymed-jlp
- fixed query string generation of rpc endpoints issue #22
- Support was dropped for generating the query string given many ids in case of an rpc endpoint. If your application has some psql functions which parse the standard input, I recommend to rework your db design. If this change causes strong damage to your application, please contact me in order to find a proper generic solution. Query strings of single rpc calls now drop the operator (
eq.) and are generated properly.
- deployment error
- fixed the last fix of getMany and getManyReferecnce for compound keys :)
- fixed getMany and getManyReferecnce for compound keys
- removed requirement to define order key in react admin, when using compound keys: default was
id, now it's the compound key
- refactored compound primary keys:
For single custom keys wrap an array as follows:
const dataProvider = postgrestRestProvider(API_URL, fetchUtils.fetchJson, 'eq', new Map([ ['some_table', ['custom_id']], // <- instead of ['some_table','custom_id'] ['another_table', ['first_column', 'second_column']], ]));
- #14, added compound primary keys (see README.md) - @programmarchy
import React from 'react';->import * as React from 'react';- Some minor code cleanup
- Fixed wrong support statement concerning postgrest starter kit in readme
- Fixed bug when multidelete - @colonist4096
- #5, Fixed bug while using multiple filters on the same attribute - @olivierdalang
- initial release