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
(I've changed the contents of each binary string value, but note that they are stored correctly). However, I note that the two name-value elements of AuthorizedLimiting both have an empty name.
If FromBSON is called on this BSON document, then what results is an instance of AuthorizedLimiting with both token and secret bytestrings set to the value associated with the first name-value pair.
A possible fix I guess might be to explicitly name the token and secret in the declaration, but I thought I'd raise this with you first, as I guess this is an example of a failure to correctly generate or extract from BSON.
thanks,
Stephen.
The text was updated successfully, but these errors were encountered:
Hi,
I have noticed an odd error in a derived instance of FromBSON (and possibly ToBSON) for a type with a particular structure. I illustrate below.
ToBSON seems to work ok, the following being an example of what is generated (ie. show $ toBSON x):
(I've changed the contents of each binary string value, but note that they are stored correctly). However, I note that the two name-value elements of AuthorizedLimiting both have an empty name.
If FromBSON is called on this BSON document, then what results is an instance of AuthorizedLimiting with both token and secret bytestrings set to the value associated with the first name-value pair.
A possible fix I guess might be to explicitly name the token and secret in the declaration, but I thought I'd raise this with you first, as I guess this is an example of a failure to correctly generate or extract from BSON.
thanks,
Stephen.
The text was updated successfully, but these errors were encountered: