Refactor Contact class methods to be async

[use-tusk]

This pull request makes all public methods in the Contact class asynchronous, ensuring consistent use of await in future implementations. Changes include updating method signatures to return Promise where applicable and ensuring compatibility with related classes like ContactSelf. No external behavior of the class has been changed, but the internal handling is now fully asynchronous.

---

Tips:

• Make sure to test changes before merging.
• Submit a "Request Changes" review and I'll address it.
• Close this PR if it's obviously incorrect. This will improve my future PRs.
• Go to the Tusk activity logs to see more details.

---

🚀 This description was created by Ellipsis for commit 159e84c

Summary:

Refactored Contact class methods name, title, and coworker to be asynchronous, ensuring future compatibility and consistency in handling asynchronous operations.

Key points:

• Refactor Contact class methods to be asynchronous.
• Update name, title, and coworker methods to return Promise.
• Ensure compatibility with related classes like ContactSelf.

---

Generated with ❤️ by ellipsis.dev

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[huan]

Hey @ellipsis, give me a code review

[ellipsis-dev]

OK! Reviewing this PR...

---

Responding to this comment by @huan. For more information about Ellipsis, check the documentation.

[ellipsis-dev]

❌ Changes requested.

• Reviewed the entire pull request up to 159e84c
• Looked at 50 lines of code in 1 files
• Took 44 seconds to review

More info

• Skipped 0 files when reviewing.
• Skipped posting 0 additional comments because they didn't meet confidence threshold of 50%.

Workflow ID: wflow_iyaOdOeasx1bFvEt

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with review rules, user-specific overrides, quiet mode, and more. See docs.

⌛ 6 days left in your free trial, upgrade for $20/seat/month or contact us.

[ellipsis-dev]

The use of Promise.resolve is unnecessary in async functions. You can directly return the value. For example:

Suggested change

	async name (): Promise<string> {
	return (this.payload && this.payload.name) || ''

This comment applies to the title and coworker methods as well.