Shane Krueger
Shane Krueger
Version 1.x will retain whatever COM support is currently available. Version 2.x will not include any specific code to support COM scenarios.
Thanks for the info and support! While QRCoder 1.x will always be around for that use case, we can also readd empty constructors, backport bug fixes, or whatever is needed...
I just looked up what you're referring to -- the swiss QR code regulations on invoices. Seems that additional regulations are going into effect this November. Perhaps we should consider...
We could publish a NativeAOT dll to wrap the exact functionality required with COM wrappers so it could be used in these scenarios without additional dependencies... (but it might be...
Sorry, I know little about the Conventions project, and it seems you have a solution anyway.
Well, there would be no way for the system to know which argument to parse first. Perhaps we should add another method (e.g. `.ValidateArguments`) which is passed the context and...
ValidateArguments, if it has access to ValidationContext, could rewrite arguments also
Sounds like a great idea!
You'd probably have to make a custom scalar to allow this however.
Which also means it's a breaking change unfortunately.