Solved issue #17
closing previous PR because of fork issues.
Wrote function to check valid move.
Wrote function to check valid direction.
Wrote function to get final direction by providing validated input .
Wrote function to get final direction by providing unknown input type .
added test cases for all the above functionality .
added test case suggested by Raj
Can the other closed pr be marked as duplicate instead?
When raising a new pr on the same change. Keep a link of old pr in the description with mentioning the reason for new pr and why the other one is stopped/closed.
Make changes which are suggested on the former pr.
In Descriptions/commit messages - Explain what is added instead of keeping 'as suggested'/'as discussed' alone as the other person may not catch that. Avoid typos/spell errors.
Solved issue #17 closing previous PR because of fork issues. Wrote function to check valid move. Wrote function to check valid direction. Wrote function to get final direction by providing validated input . Wrote function to get final direction by providing unknown input type . added test cases for all the above functionality . added test case suggested by Raj