Crates.io | parse-sap-atom-feed |
lib.rs | parse-sap-atom-feed |
version | 1.2.2 |
source | src |
created_at | 2023-09-04 16:01:50.276223 |
updated_at | 2024-09-17 17:19:44.38704 |
description | Parse an XML atom:Feed received from an SAP V2 OData service using code generated by crate parse-sap-odata |
homepage | |
repository | https://github.com/ChrisWhealy/parse-sap-atom-feed |
max_upload_size | |
id | 963329 |
size | 150,829 |
atom:Feed
received from an SAP V2 OData ServiceThis crate is designed to work in conjunction with the source code generated by the parse-sap-odata
crate.
parse-sap-odata
at Build TimeThe functionality in crate parse-sap-odata
is invoked by a Rust build script in the business application that interacts with an SAP V2 OData service. The build script generates a pair of Rust modules (one for the service document, and the other for the metadata document) containing all the struct
s and enum
s needed to interact with the OData service at runtime.
parse-sap-atom-feed
at RuntimeThis crate then uses the modules generated above to consume the atom:Feed
XML returned when interacting with the OData service.
Version | Task | Description |
---|---|---|
1.2.2 | Fix | Correct decimal parser when encountering zero |
1.2.1 | Chore | Add categories to Cargo.toml |
1.2.0 | Fix | Rewrite custom decimal deserializer |
1.1.5 | Fix | Short circuit custom decimal deserializer to return zero if passed an empty string |
1.1.4 | Fix | Bump quick_xml dependency version. Update docs |
1.1.3 | Fix | Consolidate atom dependencies |
1.1.2 | Fix | Update license |
1.1.1 | Fix | Update docs |
1.1.0 | Feature | Custom parser for rust_decimal::Decimal values |
1.0.1 | Fix | Remove redundant code |
1.0.0 | Release | Promote to version 1.0 |
0.2.9 | Chore | Handle all test failures without panic |
0.2.8 | Feature | Implement std::str::FromStr for Atom types |
0.2.7 | Feature | Parse an Atom feed of <entry> elements |
0.2.6 | Feature | As per https://validator.w3.org/feed/docs/atom.html#requiredEntryElements, the Atom <content> element should either contain or link to, the complete content of the entry.If the src attribute is present, then the <properties> element (if present) exists as a sibling of the <content> element.If the src attribute is missing, the <properties> element must exist as a child of the <content> element.Add support for out-of-order XML elements (quick-xml feature overlapped-lists ) |
0.2.5 | Feature | Read generic OData service document |
0.2.4 | Fix | Update Cargo.toml dependency versions |