-
Notifications
You must be signed in to change notification settings - Fork 32
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
feat(dynamite): always send parameters even when being the default #1292
Conversation
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.
The change to the parameter doesn't make sense. Only the check if the value matches the default value has to be removed.
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.
Looking at the fixtures it seems like empty values are added?
Also the fixtures need to keep the regexes otherwise they don't work.
I'll double check. Maybe I need to do everything at once in a big PR. UriTemplate does not do so so probably some issue got introduced when rebasing. |
Can you show me where? I can't find any broken one. |
I think you where referring to the parameters that default to an empty string. I'll fix the fixtures (re add the reggexes that got removed for the parameters) and try to figure out why the tests are failing. |
2306634
to
c05a18a
Compare
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.
LGTM, but it would have been easier if you explained from the start why the default values can no longer be present in the method header. Just from this diff alone it doesn't make sense so it is better to explain why you did it.
c05a18a
to
181ebae
Compare
I find it still confusing that there is no equals sign when the value is an empty string but if that is correct I don't care 🤷♀️ |
I'll take a look. Totally forgot to verify that. |
Ok it is wrong
it will get even funnier as we must also add the |
Yes I think we need to have both changes at once. I think you could change the target branch of the other PR to this branch and then we merge the other PR into this one and merge this PR in the end |
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.
Please rebase on the main branch to ensure everything is working correctly.
Signed-off-by: Nikolas Rimikis <[email protected]>
Signed-off-by: Nikolas Rimikis <[email protected]>
Signed-off-by: Nikolas Rimikis <[email protected]>
334d403
to
06e2eef
Compare
This is odd 🤔 |
This is really strange indeed. I can reproduce it locally 🤔 |
Also fails on the main branch. Switching to 27.0.1 works |
I rebuild the image without any cache locally and it works again... |
I deleted the tagged version of the image and restarted the CI and now it works 🤷♀️ |
fixes: #1281