-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update HttpRequest.cpp.mustache - use stable 4-parameter connect #18893
Conversation
Use stable 4-parameter connect
thanks for the PR. please follow step 3 to update the samples. cc @ravinikam (2017/07) @stkrwork (2017/07) @etherealjoy (2018/02) @MartinDelille (2018/03) @muttleyxd (2019/08) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, please do the step 3 though
I ran the parts of step 3, committed and pushed. Put I don't see a hint that these changes came in. Any hint what might went wrong? |
Ah wait - I pushed to my |
Reviewing the changes I see a lot of path separator changes, obviously because I ran mvn and the scripts on Windows. Is that really what you want? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please push only the change regarding HttpRequest please!
@muttleyxd @MartinDelille when you guys have time, can you please PM me via Slack? Thanks. |
This reverts commit 1d4e78a.
As far as I see there is nothing changed but the manual change in HttpRequest, as long as the shifted entries of From a Windows user perspective the script I was asked to follow in step 3 is unusable in this state. Maybe it should be extended to replace all I don't have the time to dig into it but the git bash seems to have commands for this:
|
@Jazzco tests with updated samples failed: https://github.com/OpenAPITools/openapi-generator/actions/runs/9527512386/job/26264196606?pr=18939 can you please review the test failure when you've time? |
@wing328 I reviewed the change and don't see what could cause the issue. As mentioned above, step 3 produces many line break changes when processed on Windows, so I reverted it. Maybe I oversaw a generated change that was necessary but I guess it makes way more sense to run this script on Linux in the current state. Locally generating our api and patching the results with these two changes afterwards works fine. @ravinikam (2017/07) @stkrwork (2017/07) @etherealjoy (2018/02) @MartinDelille (2018/03) @muttleyxd (2019/08) Regards |
I sent you an email! |
…tion (see warning [clazy-connect-3arg-lambda])
I noticed that there were some other [clazy-connect-3arg-lambda] warnings, this time in api-body, and fixed them, too. |
To get this right I ran step 3 from a Linux vm and pushed the generated changes now. |
I tested these changes using Qt 5.15.2 on Windows. There were no compilation or link errors. |
There were () missing and it obviously worked with the 3 param version but failed with the 4 param version under macOS. Hopefully it builds now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you so much for your contribution!
the CI tests failed: https://github.com/OpenAPITools/openapi-generator/actions/runs/9567139672/job/26402928612?pr=18893 please take a look when you've time. |
updated again |
@Jazzco can you make sure you have regenerated the sample accordingly ? |
done |
@wing328 It looks like the CI wasnt' triggered properly. Any idea why ? |
There was a timeout warning. Maybe some resources were busy. I merged master in again to trigger a rebuild. |
Looks better now |
…-body.mustache Co-authored-by: Martin Delille <[email protected]>
Now it complains in "Samples up-to-date" but I did update the samples, all 3 steps. |
did you do |
Yes, all 3 steps: mvn clean, generate samples, and generate docs |
Also repeated the steps and git states there's nothing to commit. |
Looks stable now, doesn't it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I was back from vacation yesterday. I see only one last issue with your changes (see other comment).
// https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#style-values | ||
if ($openApiType === 'array' && $style === 'deepObject' && $explode) { | ||
return $value; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change looks like to be not related to the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, that's not my code. How did it come in? What am I supposed to do now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An easy fix would be just to remove it. Check there is no difference with master using git diff martin...patch-1
before committing.
@MartinDelille Will this be merged for the 8.0.0 release? Is anything missing? |
@Jazzco I'll take another look tomorrow if i understand it correctly, this is not a breaking change, right? |
@Jazzco please also PM me via Slack when you've time: https://join.slack.com/t/openapi-generator/shared_invite/zt-12jxxd7p2-XUeQM~4pzsU9x~eGLQqX2g thank you |
just reviewed again and looks good thanks again for the PR |
The 3-parameter connect is known to cause issues when the creating instance is deleted. In all other mustache you already use stable 4-parameter connect. In
HttpRequest.cpp.mustache
the fix was missing.PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master
(upcoming 7.6.0 minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)