Not a Fan of Conflict

3 days!! I have been working on my CLI non-stop 3 days. Finally, I can present you something. I am so involved with this project. As this project’s each and every little decision is completely made by me, I can truly say it is MY PROJECT. So, I try to “perfect” it as much as I can.

Before going to the lab, a little update: I updated my tool with some additional feature such as handling redirect status code, passing files from multiple directories and passing multiple URL. You are welcome to check it out.

For this week’s lab I chose following features though I am hoping to add all of them in future:

Feature One

After all those question going around my mind, I found a solution: I can pass a configuration file(a valid json file) as my argument where the user can specify the result type good, bad or all. TADA! Here’s how I check if the config file exists or not and if they pass an absolute path or not.

Image for post
Image for post

Based on configuration file’s result type, the user will see different results. If user does not specify the result type, the default is all. Here is the commit where you can see how I implement it.

Image for post
Image for post
Different output based on config file’s result type

Feature Two

Image for post
Image for post
Output in JSON format

GitHub Branches and Merges

The conflict begins when I tried to merge my second issue.

Image for post
Image for post
Merge Failed
Image for post
Image for post
Merge Conflict

Fixing the conflict was not hard, but it is tedious. I resolved the conflict, made final edit and merged my second issue to master.

Anything I would do different?

Written by

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store