* Fix remove post dialog
* Consolidate mod action logic
* Make mod action form less janky
* Move content action dropdown to its own component
* Make reusable component for content action buttons
* Finish up mod dropdown
* Introduce new content dropdown component to post listing
* Fix cancel moderation button bug
* Add icons, tweak UI
* Handle delete/undelete icons
* The thing
* Fix some of the banning related bugs
* Fix mod form ban bugs
* Fix some more bugs
* Make comments use dropdown menu
* Use mod action form with comments
* Make confirmation modal
* Make all the mod action dialogs modals
* Tweak modal
* Fix bug with mod form submit
* Tweak modal more
* More modal tweaking and some feedback toasts
* Use icon pairs for on/off
* Make modals auto focus input
* Implement PR suggestions
* Make UI use async functions where needed
* Make loading state for context action modals
* Hide context actions that users should not be able to do
* Add loading state to confirmation modals
* Use updated translations
* PR feedback
* Add forgotten trnslations
* Fix scrolling bug
---------
Co-authored-by: SleeplessOne <insomnia-void@protonmail.com>
* Trying more ssr fixes. #2243
* Try to enforce cross-fetch again.
* Try to forward cookies.
* Try to forward cookies 2.
* Trying a new cross-fetch.
* Fixing headers
* Fixing some auth issues.
* Fixing isBanned.
* Fix shutdown.
* Pushing up some tries.
* Moving lemmyclient building into fetchInitialData functions.
wrappedhttpclient has two bugs:
1. setHeaders becomes async with errors gobbled up. this is probably not intentional and the result is not awaited at the call site
2. wrappedhttpclient overrides methods in the prototype and not the instance. this means that when a new instance is created, from then on all methdos on all wrappedhttpclients call the inner methods on the newly created client instead of their respective clients
this PR tries to fix both. it is untested so idk if it works
related: #2243
* Multi-platform Dockerfile
* Add ARM64 build to Woodpecker
* Sharp 0.32.6 is in package.json now
* Add Docker Healthcheck
* Prevent 'Inferno is in development mode' message
Currently Inferno runs in development mode because NODE_ENV=production was not set. This has a negative effect on performance, and for debugging purposes developers can override this flag in their Docker composefile.
* Fixing babel build.
* Removing node-prune.
---------
Co-authored-by: Dessalines <tyhou13@gmx.com>