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

Enhancement: Add "Message" action to contacts list #414

Closed
timbot1789 opened this issue Sep 13, 2023 · 3 comments · Fixed by #485
Closed

Enhancement: Add "Message" action to contacts list #414

timbot1789 opened this issue Sep 13, 2023 · 3 comments · Fixed by #485
Assignees
Labels
enhancement Enhancement of existing features

Comments

@timbot1789
Copy link
Contributor

Currently, the contacts list only has a few actions: go to pod, pin contact, and delete

image

Another useful action to have on this table would be to message the client. Add a button to each contact in this list that launches the "send message" modal when clicked, that prepopulates the "to" field with the webId of the contact.

@timbot1789 timbot1789 added the enhancement Enhancement of existing features label Sep 13, 2023
@andycwilliams andycwilliams self-assigned this Sep 13, 2023
@andycwilliams
Copy link
Member

Since I'm already working on #343 I can just pick this one up too. I think it'd be easier that way.

@andycwilliams
Copy link
Member

So I added the modal and now am setting it up to populate the To: field. What is the most efficient way to do this? Would it be to utilize the oldMessage parameter (I'm guessing via message.recipientPodUrl in the new message modal)?

@timbot1789
Copy link
Contributor Author

timbot1789 commented Oct 15, 2023

You should be able to pull the value of the to field from the webId of the contact, in the contactsList. Take a look at src/hooks/useContactsList.js.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement of existing features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants