nextcloud / nextcloud/contacts
Custom Relationship type, eg. "Dog" is displayed in lowercase, ie. "dog"
Open
Nobody has claimed this yet.
1. to develop
bug
feature: contacts
low
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
Describe the bug
No response
Steps to reproduce
- Go to "Contacts" app on /e/OS on an android phone
- Edit any contact
- Choose "More fields"
- Enter a Relationship and choose type "Custom"
- Enter a custom Relationship type, eg. "Dog"
- Save the edit
- On the phone, the Relationship type displays as "Dog"
- On Nextcloud web (current Murena build, based on Nextcloud 29), it displays as "dog". The default Relationship types, such as "Child" display correctly:
- Choose "Download" from the 3-dots menu
- See that in the exported VCARD file, all Relationship types are stored lowercase. So to me it seems to be a "rendering" issue.
Excerpt of VCARD file:
RELATED;TYPE=spouse;VALUE=TEXT:TestName
RELATED;TYPE=child;VALUE=TEXT:TestName
RELATED;TYPE=child;VALUE=TEXT:TestName
RELATED;TYPE=dog;VALUE=TEXT:TestName
Expected behavior
Custom Relationship types should also display starting with a capital letter
Actual behavior
Custom Relationship types display in lowercase.
Contact version
? Nextcloud 29, Murena build
Operating system
? Murena build
PHP engine version
None
Web server
None
Database
None
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the custom Relationship type in the Contacts app and compare its web rendering with the downloaded VCARD output. Trace where custom relationship labels are displayed and exported; done means a value such as "Dog" retains its capitalization in the web interface and exported VCARD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100