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
Notice that bar is missing. What's odd is that foo is serialized, despite it being referenced by name as a string, as if Cargo.toml has special handling, or perhaps that is a common enough pattern to warrant forcing serialization. But as is also common in Cargo.toml, not ever feature would be refenced.
Deserialized serialized an empty array and that's what should be serialized. I could see if an array is $null, but this may require specific handling apart from PowerShell's "emptyness" (like its "falsy" behavior) such that $null != empty for collections.
The text was updated successfully, but these errors were encountered:
Looks like a pretty gnarly bug, hopefully they can figure out the cause and push a new version. Happy to push out a release of this module when they've got a fix ready.
We are using PSToml for some Rust release pipelines and found that empty, unreferenced[^unref] arrays are not being serialized.
You can observe this with the latest version of PSToml:
Notice that
bar
is missing. What's odd is thatfoo
is serialized, despite it being referenced by name as a string, as ifCargo.toml
has special handling, or perhaps that is a common enough pattern to warrant forcing serialization. But as is also common inCargo.toml
, not ever feature would be refenced.Deserialized serialized an empty array and that's what should be serialized. I could see if an array is
$null
, but this may require specific handling apart from PowerShell's "emptyness" (like its "falsy" behavior) such that$null
!= empty for collections.The text was updated successfully, but these errors were encountered: