[Lark Documents] Add Tenant Switcher

[abnershang]

Extension

https://www.raycast.com/tmk/lark

Description

• Enable multiple tenant authorization and store the tenant info (tenant name, Lark or Feishu type).
• Search Document and Search Meeting Minutes can switch tenants and query documents under the selected tenant.
• The tenant switcher can be clicked to select or use the keyboard shortcut ⌘ + shift + P.
• Authorized tenants can be removed.

Who will benefit from this feature?

Users who have multiple tenants in both Lark and Feishu can achieve greater productivity when collaborating with multiple teams and tenants.

Anything else?

[raycastbot]

Thank you for opening this issue!

🔔 @tmkx you might want to have a look.

💡 Author and Contributors commands

The author and contributors of tmk/lark can trigger bot actions by commenting:

• @raycastbot close this issue Closes the issue.
• @raycastbot close as not planned Closes the issue as not planned.
• @raycastbot rename this issue to "Awesome new title" Renames the issue.
• @raycastbot reopen this issue Reopens the issue.
• @raycastbot assign me Assigns yourself to the issue.
• @raycastbot good first issue Adds the "Good first issue" label to the issue.
• @raycastbot keep this issue open Make sure the issue won't go stale and will be kept open by the bot.

[tmkx]

Thanks for your detailed feature request. I'd prefer to place a doc type filter here and the tenant switcher in the actions menu, as it's a less frequently used scenario for most users. It's a valuable feature, but I can't provide any timelines as I'm occupied with other commitments.

[abnershang]

Thanks for your detailed feature request. I'd prefer to place a doc type filter here and the tenant switcher in the actions menu, as it's a less frequently used scenario for most users. It's a valuable feature, but I can't provide any timelines as I'm occupied with other commitments.

Thank you for the reply, place in the actions menu would work too. No rush.

[raycastbot]

This issue has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊

[raycastbot]

This issue has been automatically closed due to inactivity.

Feel free to comment in the thread when you're ready to continue working on it 🙂

You can also catch us in Slack if you want to discuss this.