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
error[E0599]: no method named `text` found for reference `&Node<&str, &str, svgbob::sauron::prelude::Leaf, &str, AttributeValue<()>>` in the current scope
--> /opt/rustwide/cargo-home/registry/src/github.com-1ecc6299db9ec823/svgbobdoc-0.3.0-alpha.4/src/textproc.rs:297:47
|
297 | if let Some(text) = child.text() {
| ^^^^ method not found in `&Node<&str, &str, svgbob::sauron::prelude::Leaf, &str, AttributeValue<()>>`
Pinning svgbob to a specific version (e.g., 0.6.5) will permanently resolve the issue. Pinning is also beneficial for maintaining stable rendering results, since It's hard to imagine that this is covered by semver guarantees, though pinning may negatively impact compilation times on the user's end and impede the application of bug fixes. I wonder if @ivanceras could provide some guidance on this.
yvt
added a commit
to r3-os/r3
that referenced
this issue
Mar 16, 2022
Fixes [the build error][1] that occurs when the `svgbobdoc/enable`
feature is enabled, and the version of `svgbob` specified by
`Cargo.lock` is `0.6.6`, which is newer than what `svgbobdoc
0.3.0-alpha.4` was originally written for but is still supposed to be
compatible as per semantic versioning.
[1]: yvt/svgbobdoc#5
yvt
added a commit
to r3-os/r3
that referenced
this issue
Mar 16, 2022
Fixes [the build error][1] that occurs when the `svgbobdoc/enable`
feature is enabled, and the version of `svgbob` specified by
`Cargo.lock` is `0.6.6`, which is newer than what `svgbobdoc
0.3.0-alpha.4` was originally written for but is still supposed to be
compatible as per semantic versioning.
[1]: yvt/svgbobdoc#5
https://docs.rs/crate/r3/0.2.0/builds/526363
(edit: This particular breakage was fixed by #4)
The text was updated successfully, but these errors were encountered: