[BUG] [typescript-axios] Fixed to allow setting to any type when additionalProperties is a free-form object#17628
Closed
komase wants to merge 1 commit intoOpenAPITools:masterfrom
Closed
Conversation
… Object
When additionalProperties type is a Free-Form Object, such as Object, {}, or true,it is more appropriate to use any type instead of object.
This modification only affects the TypeScript Axios Clients generators.
Merged
5 tasks
Member
|
closing in favor of #17625 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes: #16494
Similar to the case when
additionalPropertiesis set to true(additionalProperties: true), I think that whenadditionalPropertiesis Free-Form Object (additionalProperties: {}), it would be better to set it toAny type.This file too (samples/client/petstore/typescript-axios/builds/test-petstore/api.ts) has
[key: string]: object;in it, which is causing a type error, but this issue will be resolved with the modifications in this PR.I'm sorry, but when I was preparing to create a PR, I realized that there is already an existing PR with a proposed fix. It seems our approaches to the solution differ, so if it turns out that my modifications are not needed, I will close my PR.
PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master(upcoming 7.1.0 minor release - breaking changes with fallbacks),8.0.x(breaking changes without fallbacks)For TypeScript, @TiFu @taxpon @sebastianhaas @kenisteward @Vrolijkx @macjohnny @topce @akehir @petejohansonxo @amakhrov @davidgamero @mkusaka