<p><b>@cbeams</b> approved this pull request.</p>

<p>utACK. I've added a couple review commits dealing with style nits, please check them out and the related new style guideline issues I've created for both.</p>
<p>And another nit: is there a reason, <a class="user-mention" data-hovercard-user-id="1449498" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ManfredKarrer">@ManfredKarrer</a> that you created the issue at <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="329617212" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq-core/issues/117" href="https://github.com/bisq-network/bisq-core/issues/117">#117</a> and then subsequently created this pull request at <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="329617818" data-permission-text="Issue title is private" data-url="https://github.com/bisq-network/bisq-core/issues/118" href="https://github.com/bisq-network/bisq-core/pull/118">#118</a>? In general, if you know that you're going to fix an issue, just create a single pull request to deal with it. This makes it easier for everyone to deal with, especially reviewers, having one thing to look at instead of two, not having to jump between the issue and PR to read the description of the problem and to see the proposed fix, etc. I notice that this also happened with the back-to-back issue and pull request combo of #1566 and #1567.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq-core/pull/118#pullrequestreview-126301234">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AkpZtn09Rtekr7OBsK5tpKr4cVV9rpA3ks5t56HOgaJpZM4Ubhrs">mute the thread</a>.<img src="https://github.com/notifications/beacon/AkpZtrYgZBbxBHcT4K--q94n_mMB8U1Vks5t56HOgaJpZM4Ubhrs.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/bisq-network/bisq-core/pull/118#pullrequestreview-126301234","url":"https://github.com/bisq-network/bisq-core/pull/118#pullrequestreview-126301234","name":"View Pull Request"},"description":"View this Pull Request on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}</script>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/bisq-network/bisq-core","title":"bisq-network/bisq-core","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/bisq-network/bisq-core"}},"updates":{"snippets":[{"icon":"PERSON","message":"@cbeams approved #118"}],"action":{"name":"View Pull Request","url":"https://github.com/bisq-network/bisq-core/pull/118#pullrequestreview-126301234"}}}</script>
<script type="application/ld+json">{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "37567f93-e2a7-4e2a-ad37-a9160fc62647",
"title": "@cbeams approved 118",
"sections": [
{
"text": "utACK. I've added a couple review commits dealing with style nits, please check them out and the related new style guideline issues I've created for both.\r\n\r\nAnd another nit: is there a reason, @ManfredKarrer that you created the issue at #117 and then subsequently created this pull request at #118? In general, if you know that you're going to fix an issue, just create a single pull request to deal with it. This makes it easier for everyone to deal with, especially reviewers, having one thing to look at instead of two, not having to jump between the issue and PR to read the description of the problem and to see the proposed fix, etc. I notice that this also happened with the back-to-back issue and pull request combo of #1566 and #1567.\r\n",
"activityTitle": "**Chris Beams**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@cbeams",
"facts": [

]
}
],
"potentialAction": [
{
"targets": [
{
"os": "default",
"uri": "https://github.com/bisq-network/bisq-core/pull/118#pullrequestreview-126301234"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 342760172\n}"
}
],
"themeColor": "26292E"
}</script>