Here is my proposed CLI for this package.
Currently, the input is a ndjson file where each line will be sent to the specified function.
One potential downfall of this organization is when one would like to perform different functions on different records in the same file.
If anyone can think of a more elegant way to get the arguments from the functions, I am open to suggestions.
… a command specific usage message.
bmpvieira left a comment
This is amazing, thank you so much!
Can you give an example of what this implementation would look like?
This is good for now, but maybe later we could refactor to do the arguments checking at the function level and avoid having to sync changes in the lib with
Would you mind adding some tests for this new feature? I'll open another issue.