-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implement Jinja Code Generation #1
Conversation
…tor default configuration to grab env vars where appropriate
pub async fn CreateFastlyService( | ||
configuration: &configuration::Configuration, | ||
params: CreateFastlyServiceParams, | ||
) -> Result<ResponseContent<crate::datadogV2::FastlyServiceResponse>, Error<CreateFastlyServiceError>> |
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.
We need to think about having an interface that only returns FastlyServiceResponse
. Maybe we can use the with_http_info
pattern that is present in Java and Python for example.
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.
good idea, the normal create_fastly_service
function can be a small wrapper around create_fastly_service_with_http_info
for example. Will test it out
Looks really good. We should solve some high level interface issues before bringing in more APIs, but this is a great start. It would also be nice to have slightly more directory structure. I'm thinking at least separate apis and models. |
uses the go generator code, modified to output Rust