Skip to content
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

fix typescript-fetch typos #12091

Conversation

chrisdrifte
Copy link
Contributor

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
  • Filed the PR against the correct branch: 3.0.0 branch for changes related to OpenAPI spec 3.0. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

It looks like there's a couple typos that cause compilation to fail. I implemented the first two changes suggested in #11870 as that is what allowed me to build in typescript 4.9.5.

I ran the shell script ./bin/typescript-fetch-petstore.sh and had test failures. I can't imagine the failures were a result of my code changes however.

I'm targeting typescript but no one is listed for that language on the technical committee.

It looks like there's a couple typos that cause compilation to fail. I implemented the first two changes suggested in swagger-api#11870 as that is what allowed me to build in typescript 4.9.5.
@HugoMario HugoMario merged commit d97e6c6 into swagger-api:master Nov 25, 2023
10 of 11 checks passed
@HugoMario
Copy link
Contributor

Thanks a lot @chrisdrifte !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants