[w3c/push-api] Correct PushMessageData (PR #382)

Give PushMessageData a clear internal concept to hold the bytes and also make it clear that it cannot be null. None of the methods were prepared to handle it being null and nothing ever creates a PushMessageData object where it is null.

Partially addresses the concerns in #380 and fixes #381.

---

I installed tidy-html5 but that appears to not work. There are no instructions provided by this repository as to how to do formatting so I guess I'm fine with that happening in an automatic follow-up cleanup commit...

One thing that I'm not familiar with is ReSpec and how it does linking so that probably needs careful review here as I'm trying to introduce some new links.


<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/push-api/pull/382.html" title="Last updated on Jul 9, 2024, 2:36 PM UTC (531a7db)">Preview</a> | <a href="https://pr-preview.s3.amazonaws.com/w3c/push-api/382/f30bf3d...531a7db.html" title="Last updated on Jul 9, 2024, 2:36 PM UTC (531a7db)">Diff</a>
You can view, comment on, or merge this pull request online at:

  https://github.com/w3c/push-api/pull/382

-- Commit Summary --

  * Correct PushMessageData

-- File Changes --

    M index.html (25)

-- Patch Links --

https://github.com/w3c/push-api/pull/382.patch
https://github.com/w3c/push-api/pull/382.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/382
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/pull/382@github.com>