Remove message-provider crate feature as it doesn't have dependencies

Cargo.toml

@@ -29,9 +29,8 @@ temp-file = "0.1.8"
 
 [features]
 default = []
-message-provider = []
-neardata = [ "message-provider", "reqwest" ]
-lake = [ "message-provider", "near-lake-framework" ]
+neardata = [ "reqwest" ]
+lake = [ "near-lake-framework" ]
 
 [[example]]
 name = "watch-the-slime"

README.md

@@ -19,6 +19,11 @@ InIndexer is a NEAR indexer framework.
 - Some helper functions and types for working with logs, balances, and other commonly used functionality in
   `near_utils`.
 
+## Feature flags
+
+- `neardata`: Neardata data source
+- `lake`: NEAR Lake data source
+
 This crate only works with tokio runtime.
 
 If you want to see some examples, check minimal examples in [examples/](examples/) or real indexers used in Intear infrastructure ([nft-indexer](https://github.com/INTEARnear/nft-indexer), [potlock-indexer](https://github.com/INTEARnear/potlock-indexer), [trade-indexer](https://github.com/INTEARnear/trade-indexer), [new-token-indexer](https://github.com/INTEARnear/new-token-indexer), [intear-oracle indexer](https://github.com/INTEARnear/oracle/tree/main/crates/indexer)). By the way, some of these repositories are libraries, so if you want the same functionality but with a different event handler, you can use them in your code by specifying them as git dependencies.

src/lib.rs

@@ -18,14 +18,18 @@
 //! - Some helper functions and types for working with logs, balances, and other commonly used functionality in
 //!   [`near_utils`].
 //!
+//! ## Feature flags
+//!
+//! - `neardata`: Neardata data source
+//! - `lake`: NEAR Lake data source
+//!
 //! This crate only works with tokio runtime.
 
 mod indexer_state;
 #[cfg(test)]
 mod indexer_tests;
 #[cfg(feature = "lake")]
 pub mod lake;
-#[cfg(feature = "message-provider")]
 pub mod message_provider;
 pub mod multiindexer;
 pub mod near_utils;