ocelot-Social-Community/Ocelot-Social
1
0
Fork 0
mirror of https://github.com/Ocelot-Social-Community/Ocelot-Social.git synced 2026-01-19 19:31:26 +00:00
Code Issues Packages Projects Releases Wiki Activity
790 Commits 104 Branches 1,559 Tags
Commit Graph

44 Commits

Author SHA1 Message Date
Lala Sabathil
12fc42973a
Merge branch 'master' into 212-change-password 2019-03-13 16:50:19 +01:00
Wolfgang Huß
460f94ea3f Add unauthenticated test to follow and shout 
close #234
 2019-03-13 14:32:15 +01:00
Lala Sabathil
2b6f7270b5
Merge branch 'master' into 212-change-password 2019-03-11 02:19:02 +01:00
Robert Schäfer
60d711bb0a Prevent to report any type 
Resouce must have a label (Post|Comment|User)
 2019-03-10 19:05:50 +01:00
Robert Schäfer
ee5c4127e6 Prevent disabling any type 
Resource must have a label Post|Comment|User
 2019-03-10 19:05:50 +01:00
Robert Schäfer
f14c903d2a Refactor: we don't need a setup object 2019-03-10 19:05:50 +01:00
kachulio1
0a31e5278c add test for correct credentials 2019-03-10 01:44:41 +03:00
kachulio1
6cba9f1fd8 remove image url 2019-03-10 00:50:16 +03:00
kachulio1
3fbe4cb2e6 add use single quotes 2019-03-10 00:48:16 +03:00
kachulio1
35339b4674 add changePassword mutation test 2019-03-09 14:50:23 +03:00
kachulio1
82ae81d8fe add changePasssword mutation 2019-03-09 14:50:23 +03:00
Lala Sabathil
8c4c7709b5
Merge branch 'master' into get_rid_of_resource_type 2019-03-08 15:44:51 +01:00
Lala Sabathil
c50c4b78d9
Merge branch 'master' into distinct-shouts-and-follows 2019-03-08 01:00:19 +01:00
Robert Schäfer
f68e289016 Fix lint 2019-03-07 22:44:43 +01:00
Robert Schäfer
0529e2b2b0 Refactor report mutation, return a proper Report 2019-03-07 22:42:32 +01:00
Matt Rider
61a45d39ea Respond with reporter, resource 2019-03-07 17:43:00 -03:00
Robert Schäfer
95e9c14cc6 Refactor report mutation/type to reduce redundancy 
We don't need to save the type of the reported resource. We can derive
it.
 2019-03-07 20:13:39 +01:00
Robert Schäfer
4596041186 Refactor mutations without Resource type 2019-03-07 20:13:25 +01:00
Robert Schäfer
1377455cda Disable/enable should return the Resource 2019-03-07 18:31:54 +01:00
Robert Schäfer
8072939458 Tiny performance improvement 2019-03-06 17:21:49 +01:00
Robert Schäfer
f40a67b7a8 Implement disabling of comments+users+posts 2019-03-06 17:13:36 +01:00
Robert Schäfer
1c34f10f96 Test refactoring: Check comments + posts 2019-03-06 17:13:36 +01:00
Robert Schäfer
5cff508bd6 Disable/enable fullfills tests 2019-03-06 01:07:04 +01:00
Robert Schäfer
0a73ddd46d Refactor: custom resolvers for moderation 2019-03-05 23:59:54 +01:00
Grzegorz Leoniec
865fdebc5f
Fixed linting issues inside tests 2019-03-05 18:58:17 +01:00
Grzegorz Leoniec
c2aea104f4
Added basic tests for follow mutation 2019-03-05 18:44:39 +01:00
Grzegorz Leoniec
4fdb1562f9
Added test for shoutedByCurrentUser flag on posts 2019-03-05 18:34:35 +01:00
Grzegorz Leoniec
a292a522e9
Fixed an issue and added basic testing for (un)shout 2019-03-05 18:30:28 +01:00
Robert Schäfer
2b7576521c Fix lint 
+ return more attributes in post factory for convenience
 2019-03-05 18:17:02 +01:00
Robert Schäfer
592f25b978 Implement update of .disabled field 2019-03-05 18:14:25 +01:00
Robert Schäfer
99cebc8d64 Implementation ready except disabled attr. 2019-03-05 17:45:10 +01:00
Robert Schäfer
f2e7e515a4 Check from: User! matches the authenticated user 2019-03-05 16:46:39 +01:00
Robert Schäfer
85d9d7043e Setup isModerator permission for disable relation 2019-03-05 16:25:01 +01:00
Robert Schäfer
420ea8a4d6 Scaffold some tests for disabledBy relation 2019-03-05 16:15:31 +01:00
Robert Schäfer
180491c08c Put isAuthor in permissions middleware 
I find it dirty to access the database in a middleware, ie. I would like
to put all access on the database as close to the resolver as possible.
However, in this case that would mean to put the authorization check in
the resolver, where nobody expects it to be.

CC @appinteractive
 2019-03-04 19:43:24 +01:00
Robert Schäfer
c869724d29 Let all tests pass 💚 2019-03-04 18:41:05 +01:00
Robert Schäfer
b2520258a3 Improve specification of posts resolver 
* only authors are alllowed to update/delete their own posts
* set disabled+deleted to false if not provided
 2019-03-04 18:41:05 +01:00
Robert Schäfer
fb2b407be0 Extend @Tirokk 's test to Create and Update 2019-03-03 14:32:29 +01:00
Robert Schäfer
f25708875a Refactor badges test 
CC @Tirokk @grenzfrequence

* the top level block should correspond with the name of the resolver
  * the block below should be `CreatePost` or `UpdatePost`
* the arguments of client.request are `query/mutation`, `variables` but
  you passed in the `headers` which should go into `new
  GraphQlClient(host, options)`
* re-use the very same mutation to avoid bugs in the tests
* use `await expect(someAsyncMethod).resolves.toEqual(expected)` style for
  extra test assurance
 2019-03-03 14:01:50 +01:00
Wolfgang Huß
6937c60ef8 Only admins are allowed to create badges 2019-03-01 15:49:11 +01:00
Matt Rider
5e592f666b Write unit test badge creation 
- for unauthenticated
- for authenticated admin

Co-authored-by: Wolfgang Huss <wolle.huss@pjannto.com>
 2019-02-28 16:16:14 -03:00
Matt Rider
f9b60fa0b0 Fix lint 2019-02-27 08:10:20 -03:00
Robert Schäfer
5fd44230dd Get rid of LoggedInUser graphql type 
This was causing a lot of headache on the frontend. Now, there a single
source of truth. If you query `currentUser` you can overwrite your local
copy of the user and update the UI.
 2019-02-27 11:08:13 +01:00
Robert Schäfer
69bf53e05e Impplement currentUser query 
* remove dead code (passport-jwt)
* refactor resolves to have a separate folder
* currentUser and login have the same response
 2019-02-26 16:35:31 +01:00