<p></p>
<p>Given our CoAP messages are built for sequential option addition, I think that the better course here would be to parse the URI once, and then have the different functions to apply the components to a message.</p>
<p>For some applications it may be convenient to have a convenience function that sets all options, but that should be documented to be a convenience function equivalent to calling this particular list of functions, so that users who do need to add options inbetween can switch over easily.</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/RIOT-OS/RIOT/pull/15830#issuecomment-764759153">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABE7WYA3GBPUUW6GKY4Z5ILS3BHNJANCNFSM4WM7GDFA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ABE7WYG6UGHZXSIOL3DWOPTS3BHNJA5CNFSM4WM7GDFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFWKUY4I.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/RIOT-OS/RIOT/pull/15830#issuecomment-764759153",
"url": "https://github.com/RIOT-OS/RIOT/pull/15830#issuecomment-764759153",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>