Skip to content

fix: add Refs generic to PluginSpecificConfiguration interface#4551

Open
lgraziani2712 wants to merge 1 commit intohapijs:masterfrom
lgraziani2712:fix/4526-add-Refs-to-plugins-route
Open

fix: add Refs generic to PluginSpecificConfiguration interface#4551
lgraziani2712 wants to merge 1 commit intohapijs:masterfrom
lgraziani2712:fix/4526-add-Refs-to-plugins-route

Conversation

@lgraziani2712
Copy link

Add Refs generic to plugins key for CommonRouteProperties, extending the generic for logic inside plugins.

This fixes situations where plugins API have lambdas where access the request object and requires to have the same Refs type from the route.

Fix #4526

…rface

Add Refs generic to plugins key for CommonRouteProperties, extending the
generic for logic inside plugins.

This fixes situations where plugins API have lambdas where access the
request object and requires to have the same Refs type from the route.
@damusix
Copy link
Contributor

damusix commented Aug 7, 2025

@lgraziani2712 existing tests passed... But I still fear breaking people's builds....

What might happen is the inverse of this

Can you add some typescript testing?

In particular, spell out your use-case in tests (Happy path).
And then make another use-case for where a user doesn't depend on ReqRefs:

In fact, if you can pnpm link to your local build against those packages and see if it breaks their typings, that could be an issue.

If there are no issues, screenshot and post here for us to see and further discuss!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve PluginSpecificConfiguration intellisense adding Refs generic

2 participants

Comments