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
If I use tags = [require('yaml/types/binary').binary] then it works. Was this an intentional change? omap and set export the type without an extra property assignment.
The text was updated successfully, but these errors were encountered:
Oh, drat. It looks like I've managed to export arrays of tag objects from yaml/types/binary and yaml/types/timestamp, and tag objects from yaml/types/{omap,pairs,set}.
This should get fixed at least so that importing and using the types "just works", but I'm considering taking the opportunity to refactor the type exports to be a bit clearer than they are now.
I've added a workaround for this specific issue by accepting arrays of tag objects in tags, and will open a separate issue regarding the package's exports more generally.
Output:
If I use
tags = [require('yaml/types/binary').binary]
then it works. Was this an intentional change?omap
andset
export the type without an extra property assignment.The text was updated successfully, but these errors were encountered: