[WIP] feat: unify table features #1404
Draft
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.
What changes are proposed in this pull request?
This PR refactors the table features implementation by unifying the separate ReaderFeature and WriterFeature enums into a single TableFeature enum, introducing proper feature type classification, and adding validation to ensure protocol correctness.
Added validate_table_features() method to Protocol that enforces:
- Reader features must be ReaderWriter type and also present in writer features
- Writer features must be either Writer type or also present in reader features (if ReaderWriter)
How was this change tested?
Fix all tests to use the unified table features