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(integration): Twenty - Initial Raycast Extension #7762

Closed
wants to merge 5 commits into from

Conversation

chrisdadev13
Copy link
Contributor

@chrisdadev13 chrisdadev13 commented Oct 16, 2024

Hey!! I made an initial version of the Raycast integration for Twenty. code

Today it was merged and added to the Raycast store, go check it out at: https://www.raycast.com/chrisdadev13/twenty 🙂. I guess we will have to do something extra(?) so instead of raycast.com/chrisdadev13/twenty we can have something like: raycast.com/twenty/twenty-crm(I got too inspired and genuinely forgot that I just had to share the source code and not wait till it was published in the raycast store, I'm sorry 😅). Still, I'm coding some extra commands and improving some things in the code for future updates.

This was my first Raycast extension and I really enjoyed working on this.

Screenshot 2024-10-16 at 12 22 06 PM Screenshot 2024-10-16 at 12 18 54 PM

Copy link

github-actions bot commented Oct 16, 2024

Welcome!

Hello there, congrats on your first PR! We're excited to have you contributing to this project.
By submitting your Pull Request, you acknowledge that you agree with the terms of our Contributor License Agreement.

Generated by 🚫 dangerJS against db033b3

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

This pull request introduces a new Raycast integration for Twenty, adding it to the available integration categories in the settings module and providing users with access to the Raycast extension.

  • Added packages/twenty-front/src/modules/settings/integrations/constants/SettingsIntegrationRaycast.ts defining the Raycast integration category
  • Modified useSettingsIntegrationCategories.ts to include Raycast in the list of available integration categories
  • Integrated link to the Raycast store (https://www.raycast.com/chrisdadev13/twenty) for users to access the extension
  • Included Raycast logo image path ('/images/integrations/raycast-logo.svg') for visual representation in the settings
  • Note: The current Raycast store link is under the developer's account, potentially requiring future updates for an official Twenty account

2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

@FelixMalfait
Copy link
Member

/award 1500

Copy link

oss-gg bot commented Oct 23, 2024

Awarding chrisdadev13: 1500 points 🕹️ Well done! Check out your new contribution on oss.gg/chrisdadev13

@FelixMalfait
Copy link
Member

Hey @chrisdadev13 this is super cool. The one thing I'm worried about is that it's likely to break as we update the standard objects... We could use the metadata API to make this more dynamic based on the workspace's fields/objects but that's probably a lot more work.

@chrisdadev13
Copy link
Contributor Author

Hey @chrisdadev13 this is super cool. The one thing I'm worried about is that it's likely to break as we update the standard objects... We could use the metadata API to make this more dynamic based on the workspace's fields/objects but that's probably a lot more work.

Ohh yes! I honestly didn't think about it at first, I wanted to cover the main standard objects at the beginning and then try to experiment to see how to integrate the metadata API with Raycast, which can add much more value to the tool and Twenty users.

Thank you so much for the feedbacks and comments, I think I'll definitely can try to add it with other changes I have in standby in my machine :)

@lucasbordeau
Copy link
Contributor

@chrisdadev13 Thanks for your contribution on this, could you please see with @Nabhag8848 on his PR #8117 to propose your changes as well ? It's best to work together on one PR than having duplicate PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants