Hi Spencer,

"Spencer Kinder" [email protected] wrote:

The other two questions still stand, but I just remembered that the user can call the functions and cli is just for testing, please ignore the second question.

The cli function is an important deliverable for the project, and is definitely not "just for" testing! You may want to review last week's lecture, since I discussed the cli function and its purpose in a reasonable amount of detail.

Also, I suggest it might be an idea to mentally replace "user" with "developer" when thinking about the project. (Or at least when posting about it.) In the software and illegal narcotics industries, "user" normally means the final end-user of a product. Most users will never see an API – it's developers who do that. (The distinction does become a bit blurred in some cases, since there are products – say, the REST endpoints exposed by enterprises like GitHub, Amazon, Azure, etc. – which essentially are just APIs.)

In this project, we are not told anything at all about end-users or what their requirements might be. Presumably, the API we're implementing is intended to be incorporated into some command-line application, but that's outside the scope of the project.

Cheers,

Arran