Allow using pointers for non param fields in input structs

[lsdch]

This PR allows using pointers fields in input structs, if they are not path/query/header/cookie parameters. This gives more flexibility to huma users, e.g. when defining resolvers

type EndpointInput struct {
  Token string `header:"Authorization"`
  User *User
}

func (i *EndpointInput) Resolve(ctx huma.Context) []error {
  user, token_valid := ValidateToken(i.Token) // user is nil if token is missing or invalid
  i.User = user 
  return nil
}

Summary by CodeRabbit

• New Features

  • Introduced support for pointer types in input structures, enhancing the resolver mechanism.
  • Added a new test to validate the functionality of pointer handling in HTTP operations.

• Bug Fixes

  • Adjusted the control flow for pointer type checks to allow for additional logic before triggering a panic.

[coderabbitai]

Walkthrough

The changes involve modifications to the findParams function in huma.go, specifically the repositioning of a pointer type check. In huma_test.go, a new type ResolverWithPointer is introduced, which includes a pointer to a string, along with a method Resolve and a corresponding test function TestResolverWithPointer to validate its functionality in HTTP operations.

Changes

Files	Change Summary
huma.go	Moved the pointer type check in the findParams function to a later point in the execution flow.
huma_test.go	Introduced ResolverWithPointer type with a pointer to a string, added Resolve method, and created TestResolverWithPointer to validate pointer handling in HTTP operations.

Poem

🐰 In the code where pointers play,
A new resolver found its way.
With strings that point and tests that cheer,
We hop along, no need to fear!
Changes made, we dance and sing,
For every fix, a joyful spring! 🌼

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.76%. Comparing base (77c7a16) to head (b5c4b69).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #565   +/-   ##
=======================================
  Coverage   92.76%   92.76%           
=======================================
  Files          22       22           
  Lines        3883     3883           
=======================================
  Hits         3602     3602           
  Misses        236      236           
  Partials       45       45           

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

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 77c7a16 and b5c4b69.

Files selected for processing (2)

• huma.go (2 hunks)
• huma_test.go (1 hunks)

Additional comments not posted (3)

huma_test.go (3)

2062-2064: LGTM!

The declaration of the new type ResolverWithPointer is correct.

---

2066-2070: LGTM!

The Resolve method of the ResolverWithPointer type is correctly implemented.

---

2072-2092: LGTM!

The TestResolverWithPointer test function is comprehensive and correctly validates the new functionality.