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
The fromBuffer method in the UR class currently does not accept a type parameter, which limits its flexibility. As the constructor of the UR class accepts a _type parameter, fromBuffer should also accept a type argument to allow for more versatile usage.
Current Behavior:
The fromBuffer method only takes a Buffer as an argument and defaults the type to 'bytes'.
The fromBuffer method should accept an optional type parameter that gets passed to the constructor of the UR class. If the type is not provided, it should default to 'bytes'.
The
fromBuffer
method in theUR
class currently does not accept atype
parameter, which limits its flexibility. As the constructor of the UR class accepts a_type
parameter,fromBuffer
should also accept atype
argument to allow for more versatile usage.Current Behavior:
fromBuffer
method only takes aBuffer
as an argument and defaults the type to'bytes'
.Expected Behavior:
The
fromBuffer
method should accept an optionaltype
parameter that gets passed to the constructor of theUR
class. If thetype
is not provided, it should default to'bytes'
.Proposed Change:
Impact:
UR
class, making it easier to work with various types of data.The text was updated successfully, but these errors were encountered: