chore: regenerate umbrella crate, fix feature propagation

bizinikiwi/pezframe/derivatives/src/lib.rs

@@ -29,8 +29,9 @@
 //!
 //! #### The first scenario
 //!
-//! The `pezpallet-derivatives` can be helpful when another pezpallet, which hosts the derivative assets,
-//! doesn't provide a good enough way to create new assets in the context of them being derivatives.
+//! The `pezpallet-derivatives` can be helpful when another pezpallet, which hosts the derivative
+//! assets, doesn't provide a good enough way to create new assets in the context of them being
+//! derivatives.
 //!
 //! For instance, the asset hosting pezpallet might have an asset class (NFT collection or fungible
 //! currency) creation extrinsic, but among its parameters, there could be things like some admin
@@ -90,9 +91,9 @@
 //! because `pezpallet-nfts` requires `CollectionId` to be incrementable.
 //! * It is desired to have a continuous ID space for all objects, both derivative and local.
 //! For instance, one might want to reuse the existing pezpallet combinations (like `pezpallet-nfts`
-//! instance + `pezpallet-nfts-fractionalization` instance) without adding new pezpallet instances between
-//! the one hosting NFTs and many special logic pallets. In this case, the original ID type would be
-//! `(AssetId, AssetInstance)`, and the derivative ID type can be anything.
+//! instance + `pezpallet-nfts-fractionalization` instance) without adding new pezpallet instances
+//! between the one hosting NFTs and many special logic pallets. In this case, the original ID type
+//! would be `(AssetId, AssetInstance)`, and the derivative ID type can be anything.
 
 #![recursion_limit = "256"]
 // Ensure we're `no_std` when compiling for Wasm.