The Future

[IshamMohamed]

The below is the list of possibilities capabilities provided by this framework to streamline the development

• Get rid of partial classes
  • Current Implementation: A class must be both partial and the name of the class must ends with Controller to make the class eligible for the async API generation.
  • Future: No need for the class to be partial however the name should end with Controller. By doing this, any qualified class shall be generated with
• Controller Route
  • Current Implementation: [host]/api/[controller_name]/async/
  • Furure: [host]/api/async/[controller_name]. This is because, I guess that the ASP.NET API Controllers must follow single responsibility principle thus, should ideally perform only one action, so it makes much sense to put the async prior to the controller before
• Qualification of Controllers
  • Current Implementation: Any controller inheriting ControllerBase is qualified.
  • Future (A): Develop a new AsyncControllerBase inheriting the ControllerBase and qualify all the controllers inheriting AsyncControllerBase
  • Future (B): Having an attribute [AsyncApiController] which inherits [ApiController]