Refactor package filename to handle-* fetch-* and output-* #371
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Started to realize an emerging pattern;
Command file does initial handling, then usually fetches (or collects) data before displaying (or transmitting) it.
Going to make that more consistent in all commands, here's a sample: use
handle-
for the "bridging" file. Basically this is the command being invoked without the input handling/validation. Or put differently, everything that happens after dry-run exits.Then there's a
fetch-*
file for collecting the data from the API. This may be different for files that collect data from disk or whatever but at least most of the "get-" should become "fetch-".And the last file is
output-*
to display the result to the user, or to write it to disk or something.I suspect that most
fetch-
stuffs can be abstracted pretty decently as part of our sdk interface, but there are some edge cases to take care of so we'll see if that holds.Also updated some logic to be able to test locally.