From ba5a2833cb8ce4182dd785204ed8abefbdf1cb01 Mon Sep 17 00:00:00 2001
From: Andrej Rasevic <andrej@rasevicengineering.com>
Date: Tue, 18 Jan 2022 13:37:00 -0500
Subject: [PATCH] exercise clatifications
---
exercises/exercise3/Exercise3_Description.md | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/exercises/exercise3/Exercise3_Description.md b/exercises/exercise3/Exercise3_Description.md
index 053e90e..ecd5c66 100644
--- a/exercises/exercise3/Exercise3_Description.md
+++ b/exercises/exercise3/Exercise3_Description.md
@@ -18,8 +18,13 @@ Details:
* logs - output the log of all of your session requests
* additionally your CLI should provide the user Usage information similar to the functionality in exercise 2
-2. Inside of __client.go__ you will implement all of your http client handlers as well as the persistence of the results of your network calls to a file on your file system. You need to handle the possible errors of any failed network call and store those results as well.
+2. Inside of __client.go__ you will implement all of your http client handlers as well as the persistence of the results of your network calls to a file on your file system. You need to store the repsonse data in the logs in JSON format. (See exercise 2 for help). Feel free to define any structs you need to impelment this functionality. You need to handle the possible errors of any failed network call and store those results as well.
+__Hint__ : The logs only need to store the following fields:
+ * request type (GET, POST, PUT or DELETE)
+ * endpoint you tried to hit
+ * success or failure
+The response of your network calls should still print out to STDOUT.
To deliver your submission you will need to commit your changes locally and push to your repo on the university gitlab server.
__NOTE__: You should not commit any executables or binaries as a result of compiling and building your application.
--
GitLab