* calculate distance between current user and queried user
* fix query for unset location
* use database to calculate distance
* rename distance to distance to me, 100% calculation done in DB
* distanceToMe tests
* lint fixes
* remove comments
* Show user teaser popover with badges, Desktop
* Refactor UserTeaser and add mobile popover support
* Avoid click propagation (WIP)
* Prevent event propagation
* Adjust alignment and font sizes
* More spacing for statistics
* Add distance, simplify user link
* Refactor location info into own component
* Add tests for UserTeaserPopup
* Refactor and test LocationInfo
* Query distanceToMe, rename distance to distanceToMe
* Update test
* Improve tests for UserTeaser, WIP
* Fix tests
* DistanceToMe on User instead of Location
* Revert "DistanceToMe on User instead of Location"
This reverts commit 96c9db00a44cd120e47bfe9534d3e066a194744c.
* Fix notifications
* Refactor UserTeaser and fix location info
* Fix group member crash
* Show 0 distance
* Fit in popover on small screens
* Allow access to profile on desktop
* Revert backend changes
* Load user teaser popover data only when needed
* Fix type mismatch
* Refactor for clarity and accessibility
* Litte refactorings and improvements
* Fix popover test
* Adapt and fix tests
* Fix tests and bugs
* Add placeholder
* cypress: adapt user teaser locator to changes
* Remove delays and scrolling
* Disable popovers in notification list and fix layout
* Remove flickering
* Make overlay catch all pointer events on touch devices
* Re-add attribute for E2E test
* Fix test, return to mouseover
* fix snapshot
---------
Co-authored-by: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
Co-authored-by: Wolfgang Huß <wolle.huss@pjannto.com>
Co-authored-by: mahula <lenzmath@posteo.de>
- Avoid possible errors, because of 'window' is only defined on browser side but not in NodeJS on client side. Check for 'typeof window' is neccessary, because if it's not defined at all you can't check for 'window !== undefined' without the same error 'window is undefined'.
I don't know where the bug originates. But it can only be that either
`previousResult` or `fetchMore` result is sometimes undefined. This
should make the function bullet-proof for these situations.
I had a chat with our moderator Daniel. He asks us to remove dots from
gmail accounts. He finds it more consistent and he has no problem to
write a mail to a gmail address without dots. He is OK to save the
email address different from how a user memorizes it.
- disable button if form.reasonCategory is falsy
- extract valuesReasonCategoryOptions to global constant
- extract reasonCategoryOptions to created lifecycle hook to keep data()
clean and use map
- extract formSchema to components/utils and test
- remove validator from formSchema and validate based on "Deep Rules" https://github.com/yiminghe/async-validator#deep-rules
- Use v-model to update reasonCategory and reasonDescription
- default to error message in English from backend
- Update template slot to use new syntax
Created a folder `utils` for PostHelpers.js.
Fixed a new incoming problem of the master with deleting Posts on the User Profile.
Co-Authored-By: mattwr18 <mattwr18@gmail.com>
