-
Notifications
You must be signed in to change notification settings - Fork 361
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
[WIP] Adds nodejs-axios codegen support #236
Conversation
Example snippet had improper declaration of convert function and request instance. Fixed and tested
Merging from remote develop branch
what about #232? |
I guess. I haven't tested out his version yet. Also didn't know about this pr before I made mine :/ . |
There is also #226. |
I'm not sure |
@ajwad-shaikh could you please take a look at this. |
@fjufju I would love to take a look, but I don't think it'll make a difference. The PR requires an approving review from one of the maintainers and I'm just another contributor. My own PR #238 is awaiting review for about a month now. The maintainers are having a tough time dealing with the shift to remote working practices. I suppose @shreys7 will be happy to take a look at this as soon as he finds time. |
Hey @someshkoli. below is an example of Nodejs-Request snippet generation
Similarly, if you notice Nodejs-Native snippets, we follow the same construct, i.e. define a option/configuration object before and then pass it to the actual library sdk function. Thus, we would like to use that syntax for axios too. e.g.
I will review it once again once you change the code generation to follow the above construct. I have some other comments too, will let you know once these changes are done. 🙂 |
Sure I'll add these changes |
I have made the above changes and made a new PR as this one has some additional unwanted changes. #245 |
Closes #135
Adds support for axios codegen as requested in #135