-
Notifications
You must be signed in to change notification settings - Fork 31
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): use http.Request in generated code #1707
Conversation
d8ed838
to
0add5dc
Compare
Shouldn't it be possible now to put the serializer into the request? Or do you think that mixes the layers too much? |
Do you mean similar to the validStatuses? I think this is to much mixing. Although I have to admit that the validStatuses shouldn't be there either |
Yeah, and I somewhat agree that the validation should not be in the request. |
So should we move the status code matching into the serializer? |
This might also make sense long term if we want to allow different response schemas per status code. |
That sounds good and should help with supporting multiple status codes 👍 |
0add5dc
to
3ae463d
Compare
3ae463d
to
f6e60fd
Compare
f6e60fd
to
2f307d1
Compare
2f307d1
to
26917bd
Compare
26917bd
to
d3b6cfa
Compare
Signed-off-by: Nikolas Rimikis <leptopoda@users.noreply.github.com>
d3b6cfa
to
c9d0b24
Compare
The last remaining piece of #1580