Google Workspace: Add file path information

[ridemountainpig]

Description

Adds the file path information to the list of accessories.
closes #14874

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for the update! 🎉

You can expect an initial review within five business days.

[thomaslombart]

Thanks for the PR! I have some pieces of feedback:

• Isn't it possible to make that a preference, like Display File Path, and show it in a different accessory instead of in the tooltip?
• Is there a more performant way to find the path of each file? Right now, there can easily be dozens and dozens of calls fired (especially since it's implemented in a recursive way) to display the file path. Also, it'd be probably better to add all of that inside the useFetch call to make all of the information display at once.

[ridemountainpig]

@thomaslombart Thanks for your review. I have added the Display file path option in the preferences. Due to the Google Drive API, we can only retrieve one parent file at a time. Therefore, I need to use a recursive method to obtain the file path. I have switched to using useCachePromise to get the file path.

[thomaslombart]

Also, it'd be probably better to add all of that inside the useFetch call to make all of the information display at once.

Can you also take a look at that? Maybe you can turn this hook into a useCachedPromise to add the file path information from there since I'm not sure it's possible to do that from useFetch.

[ridemountainpig]

Maybe you can turn this hook into a useCachedPromise to add the file path information from there since I'm not sure it's possible to do that from useFetch.

It seems that useFetch can't be used inside useCachedPromise because both are hooks that handle asynchronous data fetching independently. React hooks must be called at the top level, and combining them would violate that rule.

[thomaslombart]

Yes, that's why I'm asking to turn useFetch inside a useCachedPromise hook 🙂

[ridemountainpig]

@thomaslombart, do you mean to change it to this?

[thomaslombart]

Yes, exactly! I fixed a few things, so this PR is almost ready to merge.

[github-actions]

Published to the Raycast Store:
https://raycast.com/raycast/google-workspace

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.