{"push_id":2638139814,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"bc5b2eff64131bd6ed75c04be7995d39f8968ffc","before":"13d2958ab455a737e6ad3ec6275c5855cbabb73d","commits":[{"sha":"bc5b2eff64131bd6ed75c04be7995d39f8968ffc","author":{"name":"Egor Stambakio","email":"5fac0cae3ec52b8ce6c831040a402af5bbb6070f@users.noreply.github.com"},"message":"Allow permissions to be functions (#278)\n\nAPI changes\r\n====\r\n\r\n`modelDefinition.permissions.crudOperations` can be defined both as `booleans` and as `functions`. \r\n\r\n`edit` and `delete` permission functions should be able to act in 2 manners: `global` and `scoped to instance`. If function is called without arguments -> this is a request for `global` permissions (editor-wide, not connected to `instance`/`business object`). If a function is called with argument - it is an object with `instance` property, and it is used to define permissions for this particular object.\r\n\r\nChanges in `adjacent item` navigation: no matter which view a user is on, upon click on `next`/`prev` buttons editor navigates to `show` or `edit` view according to permissions for the instance. If instance is editable - it opens in `edit` view, otherwise `show`.","distinct":true,"url":"https://api.github.com/repos/OpusCapita/react-crudeditor/commits/bc5b2eff64131bd6ed75c04be7995d39f8968ffc"}]}
{"actor":{"display_login":"estambakio-sc"}}