Open 30350n opened 7 months ago
Have you had a chance to evaluate the effort? Would you fork the digikey-api altogether, or just implement your own subset of APIs? I might be interested to chip in, although Python isn't my primary language.
I've started to twiddle around with it a bit, but haven't really gotten anywhere. The perfectionist in me wants to do the whole API generation in a similar way as it's currently done in digikey-api
here, but ideally only when building the actual package (so that none of the generated code would actually be part of the git repository).
Things I've learned:
swagger-to
is poorly implemented and doesn't work with DigiKey swagger filesswagger-codegen-cli
(this is what digikey-api
uses) works, but generates a lot of bloat that has to be sorted through
DigiKey search is somewhat broken right now, the following things need fixing:
The
digikey-api
also seems like it's been unmaintained for quite a while now and doesn't support the new Product Information V4 endpoint, which could be helpful here.digikey-api
library