Skip to content

[FEATURE] Create generic abstracts and interfaces for repositories and services #15

@Marco-Sulla

Description

@Marco-Sulla

Even if the code is auto-generated, is cumbersome that the same code is copy-pasted very much time.
I think it's better to implement a AbstractRepository and an Repository interface, that shares the common code to all repositories created with EWA. This abstract and interfacecan be useful also to people that do NOT want to use EWA. The same think should be done also for services.

For this reason, the findByNameOfUniqueId() must be renamed simply findById(). This also improves abstraction and encapsulation. Interface for models and aggregators should also be implemented.

PS: are specific interfaces for repo and services really needed? Evaluate to eliminate them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions