Refactor/add service layer#2
Merged
Merged
Conversation
…едены к его контракту
service.go содержит базовые методы бизнес-логики. В рамках коммита реализовано: - добавлен пакет service с базовой структурой Service; - реализованы методы AddTask и NextDate; - добавлена валидация и нормализация данных (trim, обработка дат); - введены доменные ошибки (ErrEmptyTitle, ErrDateParse и др.); - API адаптирован для работы через service: бизнес-логика вынесена в service.
- Адаптирован GetTasksHandler
- Адаптирован GetTaskByIDHandler
- Адаптирован UpdateTaskHandler
- Адаптирован DoneTaskHandler()
- Адаптирован DeleteTaskByIDHandler() - Добавлен .gitignore - небольшая чистка кода в пакете api
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.
WIP: рефакторинг слоя хранения данных и введение TaskRepository
В рамках PR будет выполнен рефакторинг текущей архитектуры проекта и добавлены новые зависимости:
Цель текущих изменений — отделение API от конкретной реализации хранилища и подготовка архитектуры к возможной смене СУБД (например, PostgreSQL).