Global middleware not executing first

[MohnDoe]

Currently using middlewares to track events with @commandkit/analytics and I realized that the order is wrong, my global middleware is not executing first.

After a chatInput command /workout :
-> first log = +workout.middleware.ts in my /commands/(Users) folder
-> second log = +global-middleware.ts in my /commands folder

Those log are the first thing executing in the beforeExecute() function of each middleware.

[notunderctrl]

Hi. This is currently the expected behavior as mentioned at the end of this middleware guide.

Middleware execution (both before and after) follows a hierarchy: command-scoped middlewares run first, then directory-scoped middlewares, and finally global middlewares.

[MohnDoe]

I understand. I do feel like it should be the opposite though.

Instinctively, I expect it to go from the most general rules to the most precise rules. Don't you ?

[notunderctrl]

Fair assumption. During this implementation I assumed the most scoped middleware might need more priority over others, but I can see what you mean especially in global usage for stuff like analytics.

@twlite Thoughts on reversing the order?

[twlite]

Yes, I completely agree with this. It was initially discussed on the discord server yesterday and I asked them to open an issue regarding this.

[MohnDoe]

Maybe the developer can overwrite the order via commandkit config file ?

[notunderctrl]

cdaa5f2 should be sorted in next rc