nextcloud / nextcloud/ldap_contacts_backend
VCARD4.0 format
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 9
- Forks
- 7
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 25
Description
Hello,
I implement that plugin. Not very easy but very cool tool !
I face a difficulty.
In case of simple VCARD field like MAIL no issue.
In case of more complex field such as TEL or ADR, I don't see how I can't stick to VCARD format using coma as separator...
for ADR:
Using Dolibarr, my LDAP is filled up for address with multiple fields
- street
- postalcode
- L (city)
So that, it would be logical for me to have a mapping looking like:
ADR;TYPE=WORK:;;street;L;;postalcode;
Is there a workaround for that issue ?
For TEL,
it is slightly different.
You set up an aproach like "TEL:telephonenumber,mobile"
This does not help to fill TYPE.
It would be interesting to have
TEL;TYPE=CELL:mobile <-- this is working
but
TEL;TYPE=WORK,VOICE:telephonenumber <-- this is not working probably because of coma between work and voice (not 100% sure)
Would it be possible to tweak a bit your code to solve that 2 issues ?
Many thanks
francoisPE
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
No file, test, or entry point is named. Begin by locating the VCARD4.0 mapping for ADR and TEL, then reproduce the comma-separated field and type cases described; done means both mappings preserve the requested address components and telephone types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100