KyleSchoonover commented on pull request #1594: URL: https://github.com/apache/avro/pull/1594#issuecomment-1063387974
> Nice work. Any reason not to use a 3rd party library, eg. https://github.com/dotnet/command-line-api (still beta, but this will be the MS official parser in the fitire), or https://github.com/commandlineparser/commandline? The reason I am asking is that down the road new features need to be added. E.g. supporting multiple `-s` and `-p` files, maybe at the same time. Custom written command line parser can quickly become hard to maintain I agree that using the command line parser would be a good idea assuming we support multiple -s and -p. But this was me spending an hour doing a POC. The only reason I didn't use a library was because it hasn't been touched for 2 years (commandlineparser). As for command-line-api, I haven't looked into it, I personally would wait until it's out of beta. Looks like they are targeting .NetStandard 2.0 which shouldn't cause us compatibility issues. Speaking from experience at MS, dogfooding too early means a lot of rewrites. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
