Skip to content

fix: parse HeaderParams as multiple params and not as a schema object#162

Closed
Juhbaldissera wants to merge 1 commit into
epiphone:masterfrom
Juhbaldissera:fix/headers-as-separate-params
Closed

fix: parse HeaderParams as multiple params and not as a schema object#162
Juhbaldissera wants to merge 1 commit into
epiphone:masterfrom
Juhbaldissera:fix/headers-as-separate-params

Conversation

@Juhbaldissera
Copy link
Copy Markdown

The goal of this PR is to fix the issue #161 and make HeaderParams to have the same behavior as QueryParams

@Juhbaldissera
Copy link
Copy Markdown
Author

It's my first time trying to contribute here @epiphone! Please let me know if I missed anything 🙏

@matthew2564
Copy link
Copy Markdown
Contributor

Hi, I did already create a PR for this a few days ago - #160.

@epiphone
Copy link
Copy Markdown
Owner

Thank you for the contribution @Juhbaldissera! Let's go with #160 since that PR was opened earlier and it fixes another issue with non-schema reference types in @HeaderParams.

@epiphone epiphone closed this Jan 18, 2026
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.

3 participants