chore(deps): bump serde-saphyr from 0.0.26 to 0.0.28

[dependabot]

Bumps serde-saphyr from 0.0.26 to 0.0.28.

Release notes

Sourced from serde-saphyr's releases.

0.0.28 Property interpolation extensions and even faster builds

Significant extension of property interpolation ( @​CommanderStorm)

• Added support for default property interpolation in plain scalars: ${NAME:-default} now resolves to default when NAME is unset or explicitly empty.
• ${VAR}: Values that must be configured (DB URLs, API keys). An unset var is a misconfiguration, not something to paper over -> a loud error at parse time
• ${VAR-fallback}: Empty value is meaningful and distinct from "not configured". F.ex. PREFIX="" -> "no prefix".
• ${VAR:-fallback}: The "regular" default, so f.ex. ${PORT:-8080}
• ${VAR+text}: F.ex. ${DEBUG+--verbose} emits the flag whenever DEBUG exists in the environment, regardless of value.
• ${VAR:+text}: Same as above, but differentiating empty <-> null

Also

• Fix #120 LastWins not honored when deserializing struct. This was implemented and well tested, but only with maps.
• Reduced owning of comment strings (parsing very heavily commented YAML while discarding comments should be lighter on resources).
• Fixed indentation enforcement (@​CommanderStorm), making sure it also works for multiline scalars.
• Fixed tuple serialization (@​CommanderStorm)
• New SingleQuoted<..> and DoubleQuoted<..> wrappers to emit quoted strings. SingleQuoted may provide additional safety, as control characters will be rejected (with error), rather than written as YAML escape sequences. NullableTilde<T> is like Option and emits tilde ( ~ ) rather than null.

Faster compilation times with serde_core

serde-saphyr now avoids compiling serde_derive by default. The crate core uses serde_core instead that allows building serde-saphyr in parallel with serde_derive. However this also means that we needed to drop the previously built-in (de)serialization support for some serde-saphyr own configuration and reporting types like Options. (De)serialization support for these types can be re-enabled with the new feature serde_derived_types:

serde-saphyr = { version = "...", features = ["serde_derived_types"] }

This does not affect normal use of serde-saphyr for user data, you can still serialize and deserialize your own structs as before.

0.0.27 Comments

The major extension of this release is comments support.

The long existed wrapper Commented<..> was usable for serialization only until now. Since this release, Commented also captures a comment of the wrapped data structure:

struct DeploymentConfig {
    name: Commented<String>,
    image: Commented<String>,
    ports: Commented<Vec<Commented<u16>>>,
    labels: Commented<BTreeMap<String, Commented<String>>>,
}

would capture all comments for the elements of the structure, like

# deployment manifest
name: checkout
image: registry.example.com/checkout:v1 # container image to deploy
ports: # sequence of exposed ports
  - 80 # public HTTP
  - 443 # public HTTPS
labels: # mapping of Kubernetes labels
  app: checkout # stable app label
  tier: frontend # routing tier
"#;
</tr></table> 

... (truncated)

Commits

• 958bb94 NullableTilde implementation (#148)
• e2453d1 Integrate granit parser 0.0.6 parsing.
• 38f602d Implement DoubleQuoted and SingleQuoted (#146)
• 07fbcf7 Remove redundant #[cfg(test)]
• 3541006 Remaining issue: flow maps still bypass the simple-key limit
• 65d41ca fix: long string keys not roundtripping (#141)
• 2adf2c4 Split serde and make serde-saphyr core to depend on serde-core only. (#144)
• 07708ed fix fmt (#145)
• f2cd59c Implement <Quoted> (#140)
• 1a291ca fix: quoting support not counting trailing whitespace in keys, BOM, .. (#139)
• Additional commits viewable in compare view