feat!: ignore queryparams in matching

[kingtimm]

🔗 Linked issue

fixes #54 - inclusion of queryparameters on a path make it fail to match.

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Removed query parameters from the path before it is matched. The router did not seem to support them anyway.

My use-case was in nuxt-vitest's registerEndpoint but found others running into it.

Resolves #54

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.66%. Comparing base (db3a623) to head (35d94e5).
Report is 10 commits behind head on v2.

Additional details and impacted files

@@            Coverage Diff             @@
##               v2      #61      +/-   ##
==========================================
+ Coverage   95.63%   95.66%   +0.02%     
==========================================
  Files           4        4              
  Lines         435      438       +3     
  Branches       84       84              
==========================================
+ Hits          416      419       +3     
  Misses         19       19              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[pi0]

We need to use index check (like https://github.com/unjs/h3/blob/main/src/router.ts#L86) to handle URL like /login?returnTo=/path?foo=bar (context: unjs/h3#190)

[pi0]

Thanks for PR dear @kingtimm and sorry it is delayed. Main reason is that, the consumer libs (mainly unjs/h3) are already doing this normalization. It is not a breaking-change per-se but doing this means performance overhead of iterating string twice. Because of this i plan this in next major release to be included so we can adjust h3 router behavior while upgrading.