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>
## 🍰 Pullrequest
This will migrate our assets to an objectstorage via S3.
Before this PR is rolled out, the S3 credentials need to be configured in the respective infrastructure repository. The migration is implemented in a backend migration, i.e. I expect the `initContainer` to take a little longer but I hope then it's going to be fine. If any errors occcur, the migration should be repeatable, since the disk volume is still there.
### Issues
The backend having direct access on disk.
### Todo
- [ ] Configure backend environment variables in every infrastructure repo
- [ ] Remove kubernetes uploads volume in a future PR
Commits:
* refactor: follow @ulfgebhardt
Here: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8545#pullrequestreview-2846163417
I don't know why the PR didn't include these changes already, I believe I made a mistake during rebase and lost the relevant commits.
* refactor: use typescript assertions
I found it a better way to react to this comment: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8545/files#r2092766596
* add S3 credentials
* refactor: easier to remember credentials
It's for local development only
* give init container necessary file access
* fix: wrong upload location on production
* refactor: follow @ulfgebhardt's review
See: https://github.com/Ocelot-Social-Community/Ocelot-Social/pull/8545#pullrequestreview-2881626504
* feat(backend): pin more than one post
* add postPinnedCount query, better names for env variable
* add store and mixin for pinned posts counts
* test pinned post store
* context menu for pin posts
* fix typos
* unpin posts is always possible
* feat(backend): pin public group posts
* allow posts in public groups to be pinned by admins
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
* feat(backend): pin more than one post
* add postPinnedCount query, better names for env variable
* add store and mixin for pinned posts counts
* test pinned post store
* context menu for pin posts
* fix typos
* unpin posts is always possible
---------
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
