Corrected docs.rs links in README

Author: JulianSchmid

README.md

@@ -99,7 +99,7 @@ It is also possible to only slice one packet layer:
 
 * [`Ethernet2Slice::from_slice_without_fcs`](https://docs.rs/etherparse/~0/etherparse/struct.Ethernet2Slice.html#method.from_slice_without_fcs) & [`Ethernet2Slice::from_slice_with_crc32_fcs`](https://docs.rs/etherparse/~0/etherparse/struct.Ethernet2Slice.html#method.from_slice_with_crc32_fcs)
 * [`SingleVlanSlice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.SingleVlanSlice.html#method.from_slice) & [`DoubleVlanSlice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.DoubleVlanSlice.html#method.from_slice)
-* [`IpSlice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.IpSlice.html#method.from_slice) & [`LaxIpSlice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.LaxIpSlice.html#method.from_slice)
+* [`IpSlice::from_slice`](https://docs.rs/etherparse/~0/etherparse/enum.IpSlice.html#method.from_slice) & [`LaxIpSlice::from_slice`](https://docs.rs/etherparse/~0/etherparse/enum.LaxIpSlice.html#method.from_slice)
 * [`Ipv4Slice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv4Slice.html#method.from_slice) & [`LaxIpv4Slice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.LaxIpv4Slice.html#method.from_slice)
 * [`Ipv6Slice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv6Slice.html#method.from_slice) & [`LaxIpv6Slice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.LaxIpv6Slice.html#method.from_slice)
 * [`UdpSlice::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.UdpSlice.html#method.from_slice) & [`UdpSlice::from_slice_lax`](https://docs.rs/etherparse/~0/etherparse/struct.UdpSlice.html#method.from_slice_lax)
@@ -135,7 +135,7 @@ And for deserialization into the corresponding header structs have a look at:
 * [`Ethernet2Header::read`](https://docs.rs/etherparse/~0/etherparse/struct.Ethernet2Header.html#method.read) & [`Ethernet2Header::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.Ethernet2Header.html#method.from_slice)
 * [`SingleVlanHeader::read`](https://docs.rs/etherparse/~0/etherparse/struct.SingleVlanHeader.html#method.read) & [`SingleVlanHeader::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.SingleVlanHeader.html#method.from_slice)
 * [`DoubleVlanHeader::read`](https://docs.rs/etherparse/~0/etherparse/struct.DoubleVlanHeader.html#method.read) & [`DoubleVlanHeader::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.DoubleVlanHeader.html#method.from_slice)
-* [`IpHeaders::read`](https://docs.rs/etherparse/~0/etherparse/struct.IpHeaders.html#method.read) & [`IpHeaders::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.IpHeaders.html#method.from_slice)
+* [`IpHeaders::read`](https://docs.rs/etherparse/~0/etherparse/enum.IpHeaders.html#method.read) & [`IpHeaders::from_slice`](https://docs.rs/etherparse/~0/etherparse/enum.IpHeaders.html#method.from_slice)
 * [`Ipv4Header::read`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv4Header.html#method.read) & [`Ipv4Header::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv4Header.html#method.from_slice)
 * [`Ipv4Extensions::read`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv4Extensions.html#method.read) & [`Ipv4Extensions::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv4Extensions.html#method.from_slice)
 * [`Ipv6Header::read`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv6Header.html#method.read) & [`Ipv6Header::from_slice`](https://docs.rs/etherparse/~0/etherparse/struct.Ipv6Header.html#method.from_slice)

changelog.md

@@ -1,5 +1,9 @@
 # Changelog:
 
+## 0.14.2
+
+Corrected enum docs.rs links in README.md (for `IpSlice` & `IpHeaders`).
+
 ## 0.14.1
 
 Corrected example in README.md (replaced `ip` with `net`).

etherparse/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "etherparse"
-version = "0.14.1"
+version = "0.14.2"
 authors = ["Julian Schmid <info@julianschmid.name>"]
 edition = "2021"
 repository = "https://github.com/JulianSchmid/etherparse"

etherparse/src/lib.rs

@@ -178,7 +178,7 @@
 //!
 //! The PacketBuilder struct provides a high level interface for quickly creating network packets. The PacketBuilder will automatically set fields which can be deduced from the content and compositions of the packet itself (e.g. checksums, lengths, ethertype, ip protocol number).
 //!
-//! [Example:](https://github.com/JulianSchmid/etherparse/blob/0.14.1/examples/write_udp.rs)
+//! [Example:](https://github.com/JulianSchmid/etherparse/blob/0.14.2/examples/write_udp.rs)
 //! ```rust
 //! use etherparse::PacketBuilder;
 //!
@@ -203,14 +203,14 @@
 //! builder.write(&mut result, &payload).unwrap();
 //! ```
 //!
-//! There is also an [example for TCP packets](https://github.com/JulianSchmid/etherparse/blob/0.14.1/examples/write_tcp.rs) available.
+//! There is also an [example for TCP packets](https://github.com/JulianSchmid/etherparse/blob/0.14.2/examples/write_tcp.rs) available.
 //!
 //! Check out the [PacketBuilder documentation](struct.PacketBuilder.html) for more information.
 //!
 //! ## Manually serializing each header
 //!
 //! Alternatively it is possible to manually build a packet
-//! ([example](https://github.com/JulianSchmid/etherparse/blob/0.14.1/examples/write_ipv4_udp.rs)).
+//! ([example](https://github.com/JulianSchmid/etherparse/blob/0.14.2/examples/write_ipv4_udp.rs)).
 //! Generally each struct representing a header has a "write" method that allows it to be
 //! serialized. These write methods sometimes automatically calculate checksums and fill them
 //! in. In case this is unwanted behavior (e.g. if you want to generate a packet with an invalid

etherparse_proptest_generators/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "etherparse_proptest_generators"
-version = "0.14.1"
+version = "0.14.2"
 authors = ["Julian Schmid <info@julianschmid.name>"]
 edition = "2021"
 repository = "https://github.com/JulianSchmid/etherparse"