-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix properties not being displayed (needs testing) #3644
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3644 +/- ##
==========================================
+ Coverage 1.81% 2.07% +0.26%
==========================================
Files 113 89 -24
Lines 6130 5354 -776
Branches 1491 1492 +1
==========================================
Hits 111 111
+ Misses 5901 5125 -776
Partials 118 118
☔ View full report in Codecov by Sentry. |
@kesselb I'm a bit overwhelmed with what exactly to do. If you tell me what to do, I might try, but I currently don't have much time to dig in. So if you're dependent on me doing something, it might be easier to open a new PR... I hope that's ok with you. |
Original fix by @j-maas. Signed-off-by: Richard Steinmetz <[email protected]>
I simplified the code even further. @j-maas Thank you for the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and works.
/backport to stable5.4 |
Thanks for taking this on! ❤️ |
Where should we see this? I'm on 5.5.0, everything updated, and I'm still getting addresses rendered improperly, as here: #3736 (comment) |
@DiagonalArg This fix is about missing props in our frontend. Please open a new issue. |
This should fix #3440.
When opening a contact with custom labels as in the issue, I noticed the following error message in the console:
Since in PR #2064 there was a similar issue in another method, I suspect that the same fix can be applied here.
However, I was unfortunately not able to test this change, since I don't have a full development setup and I couldn't hack it in the browser. So you need to test that this fix is correct.