Built-In Data Level Access: Flexible & Re-Usable API

The Existing Data Level Access API has the following flaws:

• Tightly Coupled with the default Shift Entity Secure Controller end-points: It can not be re-used externally by:
  • Custom end-points on the same controller.
  • Other methods of serving data from repositories: for example Azure Functions.
  • Other sources of data (other than Shift Repositories): For example Cosmos DB containers
• The Predicate does not allow flexible operations

public ProductCategoryController(ProductCategoryRepository repository, IConfiguration configuration) : base(StockPlusPlusActionTree.ProductCategory, x =>
     x.FilterBy(x => x.ID, StockPlusPlusActionTree.DataLevelAccess.ProductCategory)
     .DecodeHashId<ProductCategoryListDTO>()
     .IncludeCreatedByCurrentUser(x => x.CreatedByUserID)
 )
 {
     this.repository = repository;
     this.configuration = configuration;
 }

Start by reading the ProductCategoryController, ProductCategoryRepository, and the existing Shift Entity Secure Controller endpoints referenced in the issue. Compare how the API handles custom endpoints, Azure Functions, and other data sources such as Cosmos DB containers; done means a reusable data-level access API with more flexible predicate operations.