David Koblas
David Koblas
FYI - this PR has been around for a long time to add support at the handler level https://github.com/graphql-go/handler/pull/43
I'm happy updating the PR, but given that it's been 2 years of silence not racing to rebase until I have some indication that it'll be merged...
While I've not read the details, the Apollo team wrote up this in May 2020. https://www.apollographql.com/blog/apollo-server-file-upload-best-practices-1e7f24cdc050/ Where the `apollo-upload-client` package is still a recommended option.
Looks like it's 7 digits in there. https://www.oecd.org/tax/automatic-exchange/crs-implementation-and-assistance/tax-identification-numbers/SPAIN-TIN.pdf
Though they're not referenced on the offical documents. https://www.interior.gob.es/opencms/ca/servicios-al-ciudadano/tramites-y-gestiones/dni/calculo-del-digito-de-control-del-nif-nie/
I've dug around a lot and I cannot find any validation algorithms for the "KLM" code set. I've got two choices: 1. Just allow them without checksum validation 2. Wait...
I worked on this in two different ways. As an interceptor, that's the "proper" way but of course means that you have to make sure it's on the chain whenever...
Would encourage a pull request that adds a timeout to the options structure.
I've been working on this... It makes sense to "fix" the year to 4 digits and perform all validation after that. Not "stress" over the +- difference for the long...
Thanks for the report. It'll be a little bit until I can dig into this in some detail but is very weird. Can you provide your `tsconfig.json` file for reference...