Add support for generating code for Spring RestClient#14
Merged
pimterry merged 7 commits intohttptoolkit:mainfrom Nov 6, 2025
Merged
Add support for generating code for Spring RestClient#14pimterry merged 7 commits intohttptoolkit:mainfrom
pimterry merged 7 commits intohttptoolkit:mainfrom
Conversation
pimterry
approved these changes
Nov 6, 2025
Member
pimterry
left a comment
There was a problem hiding this comment.
Thanks! This looks fantastic 👍
I don't think there's any need to make it fully runnable standalone, we don't do that for other Java snippets, and for most use cases I think this is perfect as-is.
I'll merge, release & pull into HTTP Toolkit now.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Missed an option to export requests using Spring Framework's RestClient, I haven't tested it in HTTPToolkit yet (I have yet to look what changes would be necessary) but the tests look good, the code is accurate.
I thought about maybe making the output runnable (within a method, imports, etc) but maybe it's a bit overkill?