quic: session.peerCertificate behaves differently than for http2

I am currently implementing a custom certificate verifier.
So I wait for the sesssion.opened promise to be fullfilled, and try to check the peerCertificate.
It is an X509Certificate {} object.
I wanted to check the fingerprint256 property. For quic it is a function, for http2 it was a property (supposedly a getter).

The current doc says:

The peer's certificate as an object with properties such as subject, issuer, valid_from, valid_to, fingerprint, etc. Returns undefined if the session is destroyed or the peer did not present a certificate.

So I think the intention is that it is also a property for quic, but it is not.

Also the docu for X509Certificate says:

x509.fingerprint256#
Added in: v15.6.0
Type:
The SHA-256 fingerprint of this certificate.

Though I can see easily what differs between these implementations.
(Of course not a big deal).

@jasnell is this really an issue?

Probably this applies to other properties as well.

Bắt đầu với các điểm vào session.peerCertificate của QUIC và HTTP/2, rồi so sánh cách X509Certificate.fingerprint256 được cung cấp. Kiểm tra tài liệu liên quan đến X509Certificate và các thuộc tính chứng chỉ của peer khác, sau đó xác minh rằng kiểu truy cập dự kiến nhất quán giữa các giao thức.