Ai Command Palette

Just a follow-up to not leave anyone (present or future) hanging - it was totally me poking around in VS Code that broke the JSON(-like) file. I deleted it as you suggested and reloaded my scripts, haven't had a single issue since.

I even wrote a simple script for Raycast to give AI Command the shortcut option + space and it's not only replaced like 3 other tools, but saved me so much time and headache.

This is great man, amazing stuff. I'd love to give back somehow - any 'buy me a coffee' type thin you use?

@Kurt Gold, I pushed some updates today you might want to checkout.

The first update included improvements to the `scoreMatches()` functiom:

• now using regex to match instead of indexOf
• not counting repeating words for better scoring
• simplified sorting function

/**
 * Score array items based on string match with query.
 * @param   {String} q   String to search for withing `arr`
 * @param   {Array}  arr String items to try and match.
 * @returns {Array}      Matching items sorted by score.
 */
function scoreMatches(q, arr) {
  var word;
  var words = [];
  var scores = {};
  var words = q.split(" ");
  for (var i = 0; i < arr.length; i++) {
    var score = 0;
    for (var n = 0; n < words.length; n++) {
      word = words[n];
      if (word != "" && arr[i].match("(?:^|\\s)(" + word + ")", "gi") != null) score++;
    }
    if (score > 0) scores[arr[i]] = score;
  }
  return sortKeysByValue(scores, "score", "name");
}

/**
 * Sort an objects key by their value.
 * @param   {Object} obj Simple object with `key`: `value` pairs.
 * @returns {Array}      Array of sorted keys.
 */
function sortKeysByValue(obj) {
  var sorted = [];
  for (var key in obj) {
    for (var i = 0; i < sorted.length; i++) {
      if (obj[key] > obj[sorted[i]]) break;
    }
    sorted.splice(i, 0, key);
  }
  return sorted;
}

The second update was to the actual command palette: (View diff on GitHub)

• I have some custom functionality that allows you to move the listbox selection up and down while still in the edittext search query field using the up and down arrow keys.
  • One problem with this functionality is that when a listbox listitem is selected via a script the API moves the visible "frame" of items so that the new selection is at the top. This is not standard behavior, and not even how the listbox behaves when you use the up and down keys inside of the actual listbox. So, I updated the functionality to better match the standard behavior.
  • Another problem is if a selection is made inside of the actual listbox frame by the user (via mouse or keyboard) the API doesn't offer any way to know which part of the list is currently visible in the listbox "frame". If the user was to re-enter the `q` edittext and then hit an arrow key the above event listener will not work correctly so I just move the next selection (be it up or down) to the middle of the "frame".

As for your localized version, the only thing I noticed not working correctly is the up/down functionality mentioned above. Both the my version and the newly updated version of this functionality expects there to only be 9 visible rows in the listbox. When you increased yours to 15 it breaks this functionality. To see it break, just go to Command Palette Settings > Show All Built-in Commands, and while still in the search query field, keep hitting the down arrow. Once you reach the 9th item in the list, the list will shift down incorrectly. It should shift down until you reach the bottom (or 15 rows in your case). To make this easier to adjust I have included the variable `visibleListItems` that just needs to be updated if you change the listbox size, then all of the functionality would work.

If you checkout this diff on GitHub you can see the new parts of `commandPalette()` you would need to implement. It's not a lot (mostly my comments) but it's a better experience for sure. Just make sure to change `visibleListItems` to 15 (or whatever number of rows you have in your listbox).

Let me know if any of this makes sense? Cheers!

Hi @femkeblanco @jduncan 

I'm facing a major problem: The scripts don't get executed when clicking it from menu file > script, Nothing happens at all.

Do you perhaps have an idea what I may be overlooking?

jduncan this script is AMAZING!! what a great idea.

thanks for developing and sharing with the community!