feat(router): expose event.context.matchedRoute

[iainsproat]

🔗 Linked issue

#499 499

❓ 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

Adds event.context.matchedRoute parameter which provides details of the route that the router matched on.

📝 Checklist

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

[codecov]

Codecov Report

Merging #500 (89027b9) into main (67055fb) will increase coverage by 0.36%.
Report is 4 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #500      +/-   ##
==========================================
+ Coverage   82.38%   82.74%   +0.36%     
==========================================
  Files          31       31              
  Lines        3508     3518      +10     
  Branches      522      528       +6     
==========================================
+ Hits         2890     2911      +21     
+ Misses        618      607      -11     

Files Changed	Coverage Δ
src/router.ts	96.29% <100.00%> (ø)
src/types.ts	100.00% <100.00%> (ø)

... and 3 files with indirect coverage changes

[pi0]

Thanks for pr and good explanations.

I have made some refactors to only expose it as event.context.matchedRotue? preserving all route match information including handlers. I hope you like it!

For now using as an advanced/experimental feature since there might be some underlying changes.