[#212] Remove extra white-space in PersonListCard

[baskargopinath]

Fixes #212

Reduced spacing between the index and name to remove the extra white-space by adjusting spacing of Hbox

Before:

After:

[canihasreview[bot]]

Click here to submit a new iteration when this PR is ready for review.

See this repository's contribution guide for more information.

[canihasreview[bot]]

v1

@baskargopinath submitted v1 for review.

• [v1 1/1] Adjust spacing

(:books: Archive)

Checkout this PR version locally

```sh git fetch https://github.com/se-edu/addressbook-level3.git refs/pr/213/1/head:BRANCHNAME ``` where `BRANCHNAME` is the name of the local branch you wish to fetch this PR to.

[baskargopinath]

okay prof @damithc i have updated the commit msg based on the specification

[damithc]

@baskargopinath

1. After making a change, use CanIHasReview to post the new version (similar to this)
2. There seems to an unrelated commit in this PR now

[canihasreview[bot]]

v2

@baskargopinath submitted v2 for review.

• [v2 1/1] Adjust spacing

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v1 and v2) (:chart_with_upwards_trend: Range-Diff between v1 and v2)

Checkout this PR version locally

```sh git fetch https://github.com/se-edu/addressbook-level3.git refs/pr/213/2/head:BRANCHNAME ``` where `BRANCHNAME` is the name of the local branch you wish to fetch this PR to.

[canihasreview[bot]]

v3

@baskargopinath submitted v3 for review.

• [v3 1/1] Fix double-whitespace by reducing HBox spacing

(:books: Archive) (:chart_with_upwards_trend: Interdiff between v2 and v3) (:chart_with_upwards_trend: Range-Diff between v2 and v3)

Checkout this PR version locally

```sh git fetch https://github.com/se-edu/addressbook-level3.git refs/pr/213/3/head:BRANCHNAME ``` where `BRANCHNAME` is the name of the local branch you wish to fetch this PR to.

[baskargopinath]

@damithc one thing i want to ask, this change will result in the ui change so we need to update ReadMe.md but should that be done in the same PR or we should create a seperate issue and PR for that

[damithc]

@damithc one thing i want to ask, this change will result in the ui change so we need to update ReadMe.md but should that be done in the same PR or we should create a seperate issue and PR for that

Yes, in the same commit. Otherwise the PR (and the commit) takes the code into an incorrect state. That said, the current screenshot can remain if it is good enough for the purpose. We don't need to update screenshots every time we change the UI in a minor way. Most likely the keeping the original screenshot will not hinder the reader in any way.

[baskargopinath]

@damithc one thing i want to ask, this change will result in the ui change so we need to update ReadMe.md but should that be done in the same PR or we should create a seperate issue and PR for that

Yes, in the same commit. Otherwise the PR (and the commit) takes the code into an incorrect state. That said, the current screenshot can remain if it is good enough for the purpose. We don't need to update screenshots every time we change the UI in a minor way. Most likely the keeping the original screenshot will not hinder the reader in any way.

okay makes sense

[damithc]

Merged, with some minor tweaks to the commit message. Thanks for the PR, @baskargopinath