You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, statusSize and statusMessages isn't supported in TerseBitstringStatusListEntry because it would bloat the size of the vc-barcode to the point where the VC wouldn't be very compact. We had to make some trade-offs with TerseBitstringStatusListEntry and this was one of them.
It does create an issue because in the newest version of Bitstring Status List, statusSize and statusMessages are stored in BitstringStatusListEntry. Here the BitstringStatusListEntry is supposed to be derived from TerseBitstringStatusListEntry, which does not support those properties.
The new definition of
BitstringStatusListEntry
includes thestatusSize
andstatusMessages
, that cannot be derived fromTerseBitstringStatusListEntry
.The text was updated successfully, but these errors were encountered: