refactor(features): remove fs and vault feature gates #2592
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove Feature Gates for File System and Vault Operations
Overview
This PR removes the feature gates for
fs
andvault
functionality, making these core operations available by default in the codebase. This change simplifies the dependency structure and ensures consistent availability of file system and vault operations across all builds.Changes
fs
andvault
feature flags fromCargo.toml
filestokio/fs
as a direct dependency to ensure file system operations are always available#[cfg(feature = ...)]
) from:Motivation
Previously, file system and vault operations were gated behind optional features, requiring explicit feature activation during builds. This led to:
By making these core features available by default, we:
Testing
Impact
Breaking Changes
fs
orvault
features will need to remove these feature flagsPerformance
Related Issues
none
Future Work
Checklist