Skip to content

Update Treaty Entity usage examples#44

Merged
afuno merged 8 commits intomainfrom
feature/SRV-359/entity_2
Dec 21, 2025
Merged

Update Treaty Entity usage examples#44
afuno merged 8 commits intomainfrom
feature/SRV-359/entity_2

Conversation

@afuno
Copy link
Member

@afuno afuno commented Dec 21, 2025

No description provided.

- 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.
@afuno afuno added this to the v1.0.0 milestone Dec 21, 2025
@afuno afuno self-assigned this Dec 21, 2025
@afuno afuno added the polish label Dec 21, 2025
- 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.
@afuno afuno marked this pull request as ready for review December 21, 2025 20:21
@afuno afuno changed the title Update documentation and refactor DTOs to entities Update Treaty Entity usage examples Dec 21, 2025
@afuno afuno merged commit bdbf0e2 into main Dec 21, 2025
23 checks passed
@afuno afuno deleted the feature/SRV-359/entity_2 branch December 21, 2025 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant