UX: Change default order of some results about amcommand

[hubertprein]

I'm glad you like it!

Regarding the issue; it's happening because of the way the plugin currently sorts the commands. Because you're searching for entries, the above results probably all have the same score. Because they are sorted in alphabetic order, the delete command comes first.

I'm thinking about using a different library when it comes to searching and giving an additional score to new/edit commands, to make sure the delete comes after them.

I'll get back on this.

[hubertprein]

@RobErskine I haven't touched the results yet, by adding an additional score of some sorts, but the fuzzy search engine has been swapped for another. The results of this engine look promising. Could you try this version out? It's already in the master branch.

[RobErskine]

@hubertprein Thanks for taking a stab at that. Eager to try it out. Candidly Craft 3 is my first real foray into Composer. To try your update do do I need to update my composer.json from "am-impact/amcommand": "dev-craft3", to "am-impact/amcommand": "dev-master", and then run composer update? Not sure if I need to install it another way or not.

[hubertprein]

This update isn't in the Craft 3 version yet. It's for Craft 2 at the moment. If it's suitable, it'll be ported to Craft 3 shortly after.

[hubertprein]

Updated for Craft 3. Simply use composer update.

It now searches in command descriptions as well.

[RobErskine]

Ah yeah I see. I knew about composer update, but didn't realize the new fuzzy engine was only implemented for Craft 2 (I had no idea it worked with Craft 2, gonna have to go back and install this on all my old builds!). Thank you for porting it to Craft 3. I love the new results!