Generalize request type: Move RequestBody from scheduling to requesthandling#2808
Conversation
✅ Deploy Preview for gateway-api-inference-extension ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @RyanRosario. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Tip We noticed you've done this a few times! Consider joining the org to skip this step and gain Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
6d122e2 to
8629abd
Compare
9a49201 to
d7eb204
Compare
|
@ahg-g Please review when you get a chance. |
d7eb204 to
8c2d3d4
Compare
zetxqx
left a comment
There was a problem hiding this comment.
Looks good, just one super nit comment on the import alias
03fef64 to
3865607
Compare
3865607 to
a592f62
Compare
There was a problem hiding this comment.
These tests are moved to requesthandling. so we should delete it
|
a592f62 mostly looks good. just some import alias should be better to use fwkrh and the scheduling/type_test.go should be removed. |
|
@zetxqx These were fixed in PR3 as that is when they became evident. I will fix them in PR2. |
b2f7b66 to
56cbdaa
Compare
|
56cbdaa looks good to me! |
56cbdaa to
2769bb3
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, RyanRosario The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…gateway-api-inference-extension#2808) Co-authored-by: Ryan Rosario <6713180+RyanRosario@users.noreply.github.com>
/cleanup
What this PR does / why we need it:
This is part of a larger refactor that allows the use of pluggable parsers.
Which issue(s) this PR fixes:
Part of #2447
Does this PR introduce a user-facing change?:
Built from 2808