1182 Commits

Author SHA1 Message Date
roschaefer
c6e4c38de8 build(deps): remove deprecated debug flags
I deprecated the debug flags myself here:
https://github.com/neo4j-graphql/neo4j-graphql-js/pull/288

You can now debug the queries run by `neo4j-graphql-js` by starting
the backend like this:

```bash
DEBUG=neo4j-graphql-js yarn run backend
```
2019-11-14 14:22:20 +01:00
Wolfgang Huß
913fcc2cdb Merge branch 'master' of github.com:Human-Connection/Human-Connection into 1710-list-and-protocol-moderation
# Conflicts:
#	backend/src/schema/index.js
#	webapp/locales/pt.json
2019-11-14 09:41:00 +01:00
Alina Beck
6213a25355
Merge branch 'master' into 1747-show-shouts 2019-11-14 09:37:54 +03:00
mattwr18
b38fde0fd0 Fix production error "User.locale" returned undefined 2019-11-13 18:00:35 +01:00
mattwr18
a0fe9cb94c
Merge pull request #2218 from Human-Connection/fix_locations_resolver
fix: return `null` for missig translations
2019-11-12 22:38:59 +01:00
mattwr18
feb65a6c9c Update property name to be more descriptive
- I wanted to trigger a build, since we had issues with our build server
today. I think this naming is more in the direction we want to go,
though. Maybe it could be makeShoutsPublic as @alina-beck used for the
translation keys... what do you think @kachulio
2019-11-12 21:19:52 +01:00
mattwr18
ecf0e5948b Commit to trigger build
- prefer variables on one line
2019-11-12 21:09:02 +01:00
roschaefer
deb4b4f698 fix: return null for missig translations
A query such as `{ notifications }` would return `null` for Locations
with a missing translation, e.g. `nameRU`. This would not happen for
queries implemented by `neo4j-graphql-js` because they nullify all
missing attributes automatically.
2019-11-12 19:14:34 +01:00
Alina Beck
6e3bd19267 set up privacy page in settings 2019-11-12 19:13:56 +03:00
mattwr18
3b5e40efaa Merge branch 'master' of github.com:Human-Connection/Human-Connection into donation-info 2019-11-12 15:18:10 +01:00
mattwr18
a215093bc3 Make Donations reactive
Co-authored-by: @alina-beck <alina.beck@mail.com>
2019-11-12 13:26:30 +01:00
mattwr18
afb443ac0d Update resolver to match one Donations node
- there should only ever be one Donations node to start off with, if
that changes in the future for some reason, then we'd need to look into
changing the match to something that makes more sense.
2019-11-11 19:14:06 +01:00
mattwr18
835a098731 Set up backend for DonationsInfo
Co-authored-by: Mike Aono <aonomike@gmail.com>
2019-11-11 18:14:33 +01:00
Wolfgang Huß
677039b786 Merge branch 'master' of github.com:Human-Connection/Human-Connection into 1710-list-and-protocol-moderation
# Conflicts:
#	webapp/pages/moderation/index.vue
2019-11-11 17:52:58 +01:00
mattwr18
46ed623cfa
Merge pull request #2111 from Human-Connection/russian-locales
added Russian to locales
2019-11-11 14:38:00 +01:00
mattwr18
f650c5cc05 Make createdAt/updatedAt non-nullable for NOTIFIED
- Follow @Tirokk PR review suggestion
2019-11-11 08:52:51 +01:00
mattwr18
780a418254 Fix lint 2019-11-11 08:52:04 +01:00
roschaefer
8e129c6001 fix: update counter when notification is read
@mattwr18 vue-apollo rocks! Taking the time to study the docs is a
rewarding investment.

My first idea was to cache the `unreadNotificationsCount` with Vuex.
But the docs of apollo even suggest to use apollo's local state as a
complete replacement of Vuex:
https://vue-apollo.netlify.com/guide/local-state.html

Then I further investigated why the updated `NOTIFIED` objects won't
update the notification counter. Turns out: They don't have an ID and
the computed property didn't fire when the notifications array would
change. I fixed both in this commit and yes, it works as expected.

No additional code required 💪
2019-11-11 08:52:04 +01:00
mattwr18
715261238a Protect against cypher injection vulnerability
- following @roschaefer PR review suggestion
2019-11-11 08:52:04 +01:00
mattwr18
f34c8f44e0 Update resolver for paginated notifications 2019-11-11 08:50:35 +01:00
Vasily Belolapotkov
dc09240c20 sync with 'master' to cleanup PR 2019-11-10 11:48:39 +03:00
Wolfgang Huß
553a3ca2cb Implement 'decide' button and functionality 2019-11-08 17:29:09 +01:00
Wolfgang Huß
49bea62fa7 Clarified comments in 'decide' resolver 2019-11-08 10:01:49 +01:00
Wolfgang Huß
3020a38de2 Rename variable 2019-11-08 09:56:18 +01:00
Wolfgang Huß
353687766e Change 'DECIDED' property 'updatedAt' to always be set 2019-11-08 09:41:28 +01:00
Wolfgang Huß
f4a62b03dc Clarify 'decide' resolver, rename to 'latest' property 2019-11-08 09:12:49 +01:00
Wolfgang Huß
526e4c642b Merge branch 'master' of github.com:Human-Connection/Human-Connection into 1710-list-and-protocol-moderation 2019-11-08 08:28:47 +01:00
Wolfgang Huß
2a23bbf101 Refactor frontend and 'reports' query again 2019-11-07 15:54:26 +01:00
mattwr18
cb2b8ddad7
Merge pull request #2148 from Human-Connection/2128-close-all-sessions
close all open sessions
2019-11-07 10:05:59 +01:00
Youri Seichter
d262ed678c close all open sessions 2019-11-06 18:32:25 +01:00
Wolfgang Huß
465314eda9 Extended decide mutation to close reports on close decision, first step
- Give REPORTED a 'closed' and 'decisionUuid' property.
- Give DECIDED a 'uuid' property.
2019-11-06 17:15:47 +01:00
Wolfgang Huß
35b802bf82 Remove definition of mutation disable 2019-11-06 15:18:24 +01:00
Wolfgang Huß
7d217148d3 Remove definition of mutation enable 2019-11-06 14:38:09 +01:00
Wolfgang Huß
a4521b4621 Use of mutation disable removed
- The mutation definition still has to be removed.
2019-11-06 09:13:08 +01:00
roschaefer
807ac00a12 Fix backend tests 2019-11-05 18:06:10 +01:00
roschaefer
61a8914989 Always normalize email in backend 2019-11-05 00:06:15 +01:00
roschaefer
bcf06dff25 Implement backend lookup with normalizeEmail 2019-11-05 00:06:15 +01:00
roschaefer
a704709ba3 fix: resolver returned undefined for nameRU
This registers the language Russian in the backend. Unfortunately, the
locations seem to be implemented with a hard coded attribute for each
language. 😞

We should refactor this.
2019-11-04 20:39:28 +01:00
Wolfgang Huß
96bc855518 Get the backend tests with decide mutation to work #2 2019-11-04 19:13:15 +01:00
Wolfgang Huß
f826039777 Get the backend tests with decide mutation to work #1 2019-11-04 18:33:55 +01:00
Joseph Ngugi
9668351279 add allowShouts type 2019-10-31 21:22:10 +03:00
Wolfgang Huß
21e82d2ea5 Get decide mutation to work
- Tests are not fully working yet!
2019-10-30 19:07:51 +01:00
Wolfgang Huß
54be7782ba First refactoring tests to new database structure 2019-10-30 16:59:24 +01:00
Wolfgang Huß
47d5cc89dd Implement last property on DECIDED relation 2019-10-30 15:48:46 +01:00
Wolfgang Huß
7b3224327e Prepare backend for next implementation step 2019-10-30 13:51:00 +01:00
Wolfgang Huß
8db667c1eb Refactor disable and enable mutations to decide 2019-10-28 14:07:44 +01:00
Wolfgang Huß
6593c6ec5c Refactor the database structure from DISABLED to DECIDED relation
- First Step.
- Apply properties to the relation.
2019-10-25 16:51:47 +02:00
roschaefer
2a9e182649 fix: performance issue with ordering
@mattwr18 @aonomike
You must never `ORDER BY` a property with a `@cypher` directive. Reason:
The order by performance will be terribly poor.

See my issue:
https://github.com/neo4j-graphql/neo4j-graphql-js/issues/239
And my PR:
https://github.com/neo4j-graphql/neo4j-graphql-js/pull/247
2019-10-22 20:00:12 +02:00
mattwr18
46fd534a28
Merge pull request #1840 from Human-Connection/1205-pinned-post-for-admins
Allow admins to pin a post
2019-10-21 14:37:14 +02:00
mattwr18
9d37099984
Merge pull request #1957 from Human-Connection/1955_refactor-reports-resolver-spec
Refactor reports resolver spec
2019-10-21 13:22:17 +02:00