NationTech/yaserde
6
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Avoid rustdoc testing the code under rust crate-level block

Browse Source
This commit is contained in:
Roman Valls Guimera 2021-02-08 21:36:03 +11:00
parent db005b568f
commit e412777f36
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
yaserde/src/lib.rs
View File

@ -13,7 +13,7 @@
//! file for microcontrollers is called [SVD](https://github.com/rust-embedded/svd/) //! file for microcontrollers is called [SVD](https://github.com/rust-embedded/svd/)
//! and it can be defined on YaSerDe via structs like so: //! and it can be defined on YaSerDe via structs like so:
//! //!
//!``` //!```verbatim
//! use yaserde_derive::YaSerialize; //! use yaserde_derive::YaSerialize;
//! //!
//! #[derive(Default, PartialEq, Debug, YaSerialize)] //! #[derive(Default, PartialEq, Debug, YaSerialize)]
@ -28,14 +28,14 @@
//! #[yaserde(child)] //! #[yaserde(child)]
//! devattributes: DevAttrs //! devattributes: DevAttrs
//! } //! }
//! (...)
//!``` //!```
//! //!
//! The interspersed `#[yaserde()]` macros give some indication of what the resulting XML //! The interspersed `#[yaserde()]` macros give some indication of what the resulting XML
//! Will look like, namely, a short snippet of the struct above in XML would be depending on //! Will look like, namely, a short snippet of the struct above in XML would be depending on
//! concrete values passed to the struct (not shown): //! concrete values passed to the struct (not shown):
//! //!
//!``` //!```xml
//! (...)
//! <device schemaversion: "1.0-example", xmlns: "ns:.... example" //! <device schemaversion: "1.0-example", xmlns: "ns:.... example"
//! xsnonamespaceschemalocation: "foo_bar_baz"> //! xsnonamespaceschemalocation: "foo_bar_baz">
//! <devattributes> //! <devattributes>
@ -57,7 +57,7 @@
//! ... I'm sure there are good reasons, just wanted to leave this like this so that the author //! ... I'm sure there are good reasons, just wanted to leave this like this so that the author
//! can chip in and comment about the reasons behind that decision.](https://github.com/media-io/yaserde/issues/22) ... **I personally think that issue #22 should be reopened and fixed properly (as in only requiring yaserde as a dependency, adding yaserde_derive as a feature).** //! can chip in and comment about the reasons behind that decision.](https://github.com/media-io/yaserde/issues/22) ... **I personally think that issue #22 should be reopened and fixed properly (as in only requiring yaserde as a dependency, adding yaserde_derive as a feature).**
//! //!
//! ``` //!```toml
//! [dependencies] //! [dependencies]
//! # serde = { version = "1.0.123", features = [ "derive" ] } //! # serde = { version = "1.0.123", features = [ "derive" ] }
//! # quick-xml = { version = "0.21.0", features = [ "serialize" ] } //! # quick-xml = { version = "0.21.0", features = [ "serialize" ] }
@ -69,7 +69,7 @@
//! //!
//! Last but not least, in order to have a nice, pretty printed XML output one can do //! Last but not least, in order to have a nice, pretty printed XML output one can do
//! //!
//! ``` //! ```shell
//! PLEASE LET THE USERS KNOW HOW TO DO THAT CLEARLY ON YASERDE??? //! PLEASE LET THE USERS KNOW HOW TO DO THAT CLEARLY ON YASERDE???
//! ``` //! ```
//! //!