* Add distance to group profile if location is defined
* Fix snapshot tests in 'webapp/pages/groups/_id/_slug.spec.js'
* Fix prop Vue warning in test 'webapp/pages/groups/_id/_slug.spec.js'
* reuse locationFragement for groups
* use better order on locationFragement parameters
* moved LocationInfo Component to correct place as its used in Group & User related context
* use size prop
* reduce changeset
* update snapshots
* remove computed property & simplify component
* more tests & updated snapshots
---------
Co-authored-by: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
* feat(backend): resize images with imagor
Open questions:
* Do we have external URLs for images? E.g. we have them for seeds. But
in production?
* Do we want to apply image transformations on these as well? My current
implementation does not apply image transformations as of now. If we
want to do that, we will also expose internal URLs in the kubernetes
Cluster to the S3 endpoint to the client.
TODOs:
* The chat component is using a fixed size for all avatars at the moment.
Maybe we can pair-program on this how to implement responsive images in
this component library.
Commits:
* do not replace upload domain url in the database
* fix all webapp specs
* refactor: remove behaviour we won't need
We don't want to apply image transformations on files, right?
* refactor: replace the domain on read not on write
* wip: webapp fixes
* refactor(backend): add another url to config
I've given up. There seems to be no nice way to tell the minio to return
a location which differs from it's host name.
* refactor: add test for s3Service
* refactor(backend): proxy minio via backend in local development
Commits:
* provide tests for message attachments
* remove S3_PUBLIC_URL config value
* refactor: follow @ulfgebhardt's review
* add missing environment variable
---------
Co-authored-by: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
* Fix console warning by adding 'common.filter' to locales
* Make 'common.filter' ident in component 'ProfileList.vue' responsive and remove default value
Problem:
When audio is directly recorded to chat, it has the correct file extension in its name ("audio.mp3"). The file object we get doesn't have an extension property though, so the file name after our modification would be "audio.mp3.undefined". Safari doesn't accept this as audio source, and I hate to say it, but I agree.
So if there is no extension, keep the existing one. Problem solved.