This is a side quest of #8558. The motivation is to be able to do dependency injection in the tests without overwriting global data. I saw the first merge conflict from #8551 and voila: It seems @Mogge could have used this already.
refactor: follow @Mogge's review
See: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8603#pullrequestreview-2880714796
refactor: better test helper methods
wip: continue refactoring
wip: continue posts
continue
wip: continue groups
continue registration
registration
continue messages
continue observeposts
continue categories
continue posts in groups
continue invite codes
refactor: continue notificationsMiddleware
continue statistics spec
followed-users
online-status
mentions-in-groups
posts-in-groups
email spec
finish all tests
improve typescript
missed one test
remove one more reference of CONFIG
eliminate one more global import of CONFIG
fix language spec test
fix two more test suites
refactor: completely mock out 3rd part API request
refactor test
fixed user_management spec
fixed more locatoin specs
install types for jsonwebtoken
one more fetchmock
fixed one more suite
fix one more spec
yet another spec
fix spec
delete whitespaces
remove beforeAll that the same as the default
fix merge conflict
fix e2e test
refactor: use single callback function for `context` setup
refactor: display logs from backend during CI
Because why not?
fix seeds
fix login
refactor: one unnecessary naming
refactor: better editor support
refactor: fail early
Interestingly, I've had to destructure `context.user` in order to make
typescript happy. Weird.
refactor: undo changes to workflows - no effect
We're running in `--detached` mode on CI, so I guess we won't be able to
see the logs anyways.
refactor: remove fetch from context after review
See:
refactor: found an easier way for required props
Co-authored-by: Max <maxharz@gmail.com>
Co-authored-by: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
* email templates with pug for all possible notification emails
* more information in emails
* Individual email subjects to all notification emails
---------
Co-authored-by: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
Co-authored-by: mahula <lenzmath@posteo.de>
* type for neo4j and neode
* fix build
* remove flakyness
* wait for neode to install schema
* remove flakyness
* explain why we wait for a non-promise
* refactor context
missing change
missing change
* adjust test setup
proper cleanup after test
* lint fixes
* fix failing test to use new context
* type for neo4j and neode
* fix build
* remove flakyness
* wait for neode to install schema
* remove flakyness
* explain why we wait for a non-promise
* fix diffent name notifications
We had emails sent with incorrect names.
This PR combines the query for the email with the user the notification
is sent to since the notification in database was correct.
The underlying problem is the unstable order in which the database can
return values. The results of the two queries were matched by id since
it was assumed that they always return the same order of elements.
lint fixes
fix typo
fix factory
fix tests
* fix tests accoridng to review
also test for the right amount of emails in every test
* separate all queries into one file each
* fix merge error
* fix lint
---------
Co-authored-by: mahula <lenzmath@posteo.de>
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* lint @typescript-eslint/recommended
* lint @typescript-eslint/recommended-requiring-type-checking
fix type not detected locally due to wierd uuid typings
missing save
error not reported locally
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* no notification when blocked
* no notifications for muted users
* move tests from emssage to notification middleware
* fix test
* also dont update unreadRoomCount when user is muted
---------
Co-authored-by: mahula <lenzmath@posteo.de>
* all users that observe a post are notified when the post is commented, except of the author of the comment, or users that blocked the commenter
* test to illustrate the behavior of notifications for observed posts
