Update copyq-clipboard-manager extension#9320
Conversation
- Merge branch \'contributions/merge-1700357404707863000\' - Pull contributions - Fixed some parts of view-clipboard-entries.tsx and package.json to pass linting. Added a new screenshot to metadata Updated CHANGELOG.md - Version 2.0! Added select-tab.tsx, a new command that allows the user to select a CopyQ tab. Completely reworked how clipboard contents are grabbed, resulting in a much faster loading time. With the rework of how clipboard contents are grabbed, preferences have been changed to allow the user to select how many clipboard entries to load.
pernielsentikaer
left a comment
There was a problem hiding this comment.
Hi 👋
Thanks for your new enhancement 🔥
When I use the commands I get a lot of crashes, check this video out:
Raycast-2hiKy0Wy.mp4
It also looks like there is some empty state flicker
I'm looking forward to testing this extension again 🔥
Request a new review when you are ready. Feel free to contact me here or at Slack if you have any questions.
- Fixed portability issue with view-clipboard-entries command - Removed more files from cache - Added code-workspace to gitignore - Stop tracking node_modules folder
|
The new command crashes If
|
I am having difficulty catching the two errors: "copyq not installed/incorrect path" and "copyq server not running". I am attempting to do try and catch, but if either of the two errors above are present, it will only show copyq path not found. When copyq is not running, running a copyq terminal command will result in "ERROR: Cannot connect to server! Start CopyQ server first." |
- Changed pictures for metadata - Ran linter on 2 files. - Restructured the code to use execSync instead of exec and states. Improved the speed of getting clipboard entries. Changed clipboard view to display items and markdown simultaneously. Fixed error handling for CopyQ not found and server not running.
- Ran linter on view-clipboard-entries.tsx - Fixed clipboard entries not parsing correctly.
|
I can't reproduce that error now, I guess we can continue 🚀 What about leaving the path not required and test against /opt/homebrew/bin/copyq and /usr/local/bin/copyq - if not found let the user add it in the preferences manually? |
I'm honestly stuck on the error handling. I can't find a way to try/catch "copyq server not running" and "copyq not found". When I attempt this, my code cannot tell the difference between the two errors, and throws the same return value for each (which is why the updated error screen includes "path not found or server not running". If I could differentiate these two errors, I could check for the path better, and potentially have the extension start the copyq server if the path is found but it is not running. If copyq is not found, it should return something like "command not found" Could you assist me with this change? |
|
@pernielsentikaer Are we good to publish this version? |
|
Thank you for your contribution! 🎉 🔔 @andrewcincotta you might want to have a look. |
|
Published to the Raycast Store: |
|
🎉 🎉 🎉 We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag. |
Description
Screencast
Checklist
npm run buildand tested this distribution build in Raycastassetsfolder are used by the extension itselfREADMEare placed outside of themetadatafolder