Skip to content

Commit

Permalink
Fixed member permission/role relations in fixtures
Browse files Browse the repository at this point in the history
no-issue

The previous relations were setup to match against "members", which is
plural, but the object_type on the permission is "member". This was
causing the permissions to not be added as a relation to the role.
  • Loading branch information
allouis committed May 2, 2019
1 parent 66f96d0 commit 0a67a25
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions core/server/data/schema/fixtures/fixtures.json
Original file line number Diff line number Diff line change
Expand Up @@ -603,7 +603,7 @@
"integration": "all",
"api_key": "all",
"action": "all",
"members": "all"
"member": "all"
},
"Admin Integration": {
"mail": "all",
Expand All @@ -621,7 +621,7 @@
"redirect": "all",
"webhook": "all",
"action": "all",
"members": "all"
"member": "all"
},
"Editor": {
"notification": "all",
Expand Down
2 changes: 1 addition & 1 deletion core/test/unit/data/schema/integrity_spec.js
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ var should = require('should'),
describe('DB version integrity', function () {
// Only these variables should need updating
const currentSchemaHash = 'fda0398e93a74b2dc435cb4c026679ba';
const currentFixturesHash = '6be3e640cb0f757d472c140e59418f54';
const currentFixturesHash = '675dbc4fa52873bff5263083db44e9f6';

// If this test is failing, then it is likely a change has been made that requires a DB version bump,
// and the values above will need updating as confirmation
Expand Down

0 comments on commit 0a67a25

Please sign in to comment.