This is amazing, but if you regularly leave yourself comments in your code (with //) you *may* need to remove them BEFORE URL-encoding. Otherwise instead of your nice set of columns and sorting your recipient gets only the portion of the query that happens before the first //, because the URL-encoding doesn't preserve newline characters (at least the VSCode plugin didn't) so the Resources.... query ends up on one line, and the // means it ignores everything after those characters.
It appears urlencoder.io preserves the newlines with %0A so hats off to them, that should help with keeping comments in place (like a commented line or an end of line comment). I tested with the plugin first so ran into this weird issue, and then tested with the site which keeps things much more consistent with how they would appear if you saved and shared the query in the portal.