Conversation
- Replaced all references to "DTOs" with "entities" across documentation, aligning with the updated terminology. - Refactored the directory structure to use `app/entities/` instead of `app/dtos/`. - Updated examples, classes, and documentation to reflect the use of entities instead of DTOs. - Removed unused DTO files and replaced them with entities where applicable.
- Replaced all mentions of "DTOs" with "entities" across CLAUDE, README, and workflow files to align terminology consistently. - Updated examples, code snippets, and directory references to reflect the new structure (e.g., `dtos` to `entities`). - Simplified explanation of entity usage in nested objects and arrays within documentation.
…ure/SRV-359/entity_2
- Removed redundant entity files and their corresponding specs (`UserRequestEntity`, `UserResponseEntity`, `FiltersEntity`, `IndexEntity`, etc.). - Moved and renamed all entity specs, organizing them under a more descriptive `requests` and `responses` sub-folder structure. - Updated references in RSpec files to reflect the new structure. - Simplified and streamlined entity attributes with improved validation and formatting rules.
…ties - Remove nested Gate::API namespace structure from controllers, entities, and treaties - Reorganize treaty files from gate/api/* to top-level directories (languages, movies, posts, users) - Simplify entity structure by removing intermediate request/response directories - Update routes configuration to reflect new non-namespaced structure - Update all related specs to work with new directory organization This change flattens the API structure, making it easier to navigate and maintain while reducing unnecessary nesting layers.
- Introduced domain-based directory structure under `app/entities/`. - Split entities into `requests`, `responses`, and `shared` modules for clarity. - Refactored entity names to follow a consistent naming convention (e.g., `Posts::Create::RequestEntity`). - Updated all documentation and examples to reflect the new entity structure. - Replaced inline nested entity definitions with reusable shared entities wherever applicable.
- Introduced `Posts::CreateTreaty` as the base class for treaty definitions. - Updated all documentation and examples to replace inline entities with structured references (e.g., `Create::RequestEntity` -> `Posts::Create::RequestEntity`). - Updated request and response definitions in treaty-related files to align with the standardized class structure. - Improved consistency across examples in API reference, cheatsheet, and core concepts documentation.
- Updated all treaty definitions to use fully qualified entity class names (e.g., `Create::RequestEntity` -> `Posts::Create::RequestEntity`). - Adjusted documentation, examples, and specs to reflect the changes. - Ensured consistent reference updates across CLAUDE, API reference, cheatsheet, core concepts, examples, and sandbox files.
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
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.