Refactor Feedback Module for Consistency and Clarity

- Updated feedback repository and service methods to use a consistent naming convention, changing `NewTenderRepository` and similar methods to `NewRepository`.
- Refactored feedback handler methods to improve clarity by renaming methods such as `ListFeedback` to `Search` and `GetFeedback` to `Get`.
- Enhanced feedback response structures to include detailed company and tender information, improving the clarity of feedback data returned to API consumers.
- Updated Swagger documentation to reflect changes in feedback response structures and endpoint paths, ensuring accurate representation of the API for consumers.
This commit is contained in:
n.nakhostin
2025-09-24 12:20:19 +03:30
parent cdf15c9d49
commit a342da193e
29 changed files with 666 additions and 702 deletions
+1 -1
View File
@@ -33,7 +33,7 @@ type companyRepository struct {
}
// NewCompanyRepository creates a new company repository
func NewCompanyRepository(mongoManager *orm.ConnectionManager, logger logger.Logger) Repository {
func NewRepository(mongoManager *orm.ConnectionManager, logger logger.Logger) Repository {
// Create indexes using the ORM's index management
indexes := []orm.Index{
*orm.NewIndex("registration_number_idx", bson.D{{Key: "registration_number", Value: 1}}),
+2 -2
View File
@@ -36,8 +36,8 @@ type companyService struct {
logger logger.Logger
}
// NewCompanyService creates a new company service
func NewCompanyService(repository Repository, categoryService company_category.Service, logger logger.Logger) Service {
// NewService creates a new company service
func NewService(repository Repository, categoryService company_category.Service, logger logger.Logger) Service {
return &companyService{
repository: repository,
categoryService: categoryService,