Skip to content
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

Feat: Add contact data from the in-page menu #251

Merged
merged 4 commits into from
Sep 11, 2024

Conversation

Merkur39
Copy link
Member

@Merkur39 Merkur39 commented Sep 9, 2024

Cette PR ajoute un nouveau contenu dans l'inline-menu.
Ce nouveau contenu va permettre d'éditer un champs d'un contact (selon le champs du formulaire focus).
Il peut être affiché via un nouveau bouton dans la liste des données ambiguës(tel,...), ou naturellement pour les champs nom et prénom, si l'un des deux est manquant dans le contact.

@zatteo zatteo changed the base branch from master to feat/stream2-part3 September 9, 2024 14:27
@Merkur39 Merkur39 force-pushed the feat/ver-592 branch 3 times, most recently from aaa0e4c to fb573b5 Compare September 10, 2024 12:52
@Merkur39 Merkur39 marked this pull request as ready for review September 10, 2024 12:52
If an autofill has already been run.

And add new button in the ambiguous menu,
for create new ambiguous value.
This property matches the fieldQualifier with
the property name of a Cozy Contact.
This removes the recently created `bitwardenToCozy`,
which played much the same role.
@Merkur39 Merkur39 force-pushed the feat/ver-592 branch 5 times, most recently from bda56a5 to 98d6701 Compare September 10, 2024 14:11
This menu is contextualized according to the current form field.
It can be displayed via a new button in the list
of ambiguous data, or naturally for the last and first name fields.
@Merkur39 Merkur39 merged commit b04fadf into feat/stream2-part3 Sep 11, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants