You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Ignore specific files when generating the client #454
Is your feature request related to a problem? Please describe.
When generating the client from open api spec, sometimes we need to prevent some specific files to be overwritten. I haven't found a native support in openapi-python-client currently.
Describe the solution you'd like
We can follow the .gitignore pattern and provide something like .openapi_python_ignore.
When you say files being overwritten, do you mean in the generated client? i.e. generate version A, update it to version B, but leave some files untouched? Or do you mean you want to ignore parts of the spec itself? If so this is likely a duplicate of #55 as that should get you where you need.
@clasnake , I think you are describing the same issue that I am facing: This generator does not seem to allow for files not generated from the spec inside the package.
After a quick browse it appears that the same methods used to in the generate command are used in the update command, seen here. This means that the package is essentially wiped every time an update command is executed as far as I can tell.
If I'm right, this means that potentially a .openapi-python-ignore is feasible with shutil, but an initial implementation may affect the generate and update commands.
Sounds like a great feature, and you’re correct in your assessment of current behavior.
Yes! Though currently we’re rather slow to respond / review 😅. I am mostly limited to weekend time at the moment.
I think it’d make sense to mirror the functionality from openapi-generator. update was just the easy alternative to full ignore functionality so you could leave metadata / external packages in place. I think it just becomes a special case of generate with prebaked ignore rules.. right? I don’t actually use update myself anymore so I could be forgetting something >_>.
In the coming weeks I may take this on and attempt an implementation. This is truly a superior generator for python clients from openapi specs. Looking forward to potentially being able to contribute in the future. Thanks! :)
Hi @dbanty -- I am curious if you think this feature belongs in this library. I certainly do, though there seem to be several plausible implementations.
Activity
emann commentedon Jul 20, 2021
When you say files being overwritten, do you mean in the generated client? i.e. generate version A, update it to version B, but leave some files untouched? Or do you mean you want to ignore parts of the spec itself? If so this is likely a duplicate of #55 as that should get you where you need.
bolbken commentedon Jul 28, 2021
@clasnake , I think you are describing the same issue that I am facing: This generator does not seem to allow for files not generated from the spec inside the package.
After a quick browse it appears that the same methods used to in the generate command are used in the update command, seen here. This means that the package is essentially wiped every time an update command is executed as far as I can tell.
If I'm right, this means that potentially a .openapi-python-ignore is feasible with shutil, but an initial implementation may affect the generate and update commands.
@emann , what I am describing is similar to what the openapi-generator tool has implemented.
bolbken commentedon Jul 28, 2021
@emann / @dbanty , I don't intend to push, but ...
dbanty commentedon Jul 28, 2021
@bolbken in order:
updatewas just the easy alternative to full ignore functionality so you could leave metadata / external packages in place. I think it just becomes a special case ofgeneratewith prebaked ignore rules.. right? I don’t actually useupdatemyself anymore so I could be forgetting something >_>.bolbken commentedon Jul 29, 2021
@dbanty Thanks for the quick, concise response.
In the coming weeks I may take this on and attempt an implementation. This is truly a superior generator for python clients from openapi specs. Looking forward to potentially being able to contribute in the future. Thanks! :)
adelevie commentedon Jul 19, 2022
Hi @dbanty -- I am curious if you think this feature belongs in this library. I certainly do, though there seem to be several plausible implementations.