Remove strategy-related documentation and code components#24
Merged
Conversation
- Eliminated mentions of `DIRECT` and `ADAPTER` strategies from all documentation files (e.g., README, migration guide, cheatsheet, and examples). - Removed strategy definitions and validations from core files (`strategy.rb` and `exceptions/strategy.rb`). - Updated examples and version definitions to exclude strategy references, simplifying the usage patterns. - Adjusted comparison tables, validation, and transformation sections to remove strategy-specific details. - Ensured performance notes and best practices align with the new streamlined approach. This cleanup aims to simplify the API by removing strategy distinctions, making it more intuitive for developers.
- Eliminated all mentions of `DIRECT` and `ADAPTER` strategies across documentation, including examples, cheatsheets, and guides. - Simplified the core code by removing references to strategy from validators and attributes, including helper methods and factories. - Updated versioning and validation logic to streamline API usage without the strategy distinction. - Adjusted best practices, use cases, and transformation examples to align with the simplified API design.
- Deleted `Strategy` exception handling and related comments from `exceptions/base.rb` and controller error handling. - Removed the definition for `unknown strategy` from locale file (`en.yml`). - Erased strategy-related notes and examples from CLAUDE documentation, including patterns and guidelines. - Updated validation base class to remove strategy-specific mentions, focusing exclusively on request and response validation. - Simplified API descriptions by eliminating strategy context in workflow and code review documentation. This further declutters the API by removing remnants of the deprecated strategy concept.
- Deleted repeated "Examples" links from `migration-guide.md`, `transformation.md`, and `validation.md` under "Next Steps" sections. - Ensures clarity by eliminating unnecessary redundancy without altering overall structure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.