The lack of Interface Resolving in Gates is knocking out the whole Repository Pattern Methodology where a Developer cannot reuse Contracts as Gate Parameters and have to choose between rewriting redundant SQL or Initiating the Repository Classes directly in Gates.
The issue has been mentioned here and here would the Dev Community consider to include this requirement in Laravel Roadmap ?
The lack of Interface Resolving in Gates is knocking out the whole Repository Pattern Methodology where a Developer cannot reuse Contracts as Gate Parameters and have to choose between rewriting redundant SQL or Initiating the Repository Classes directly in Gates.
The issue has been mentioned here and here would the Dev Community consider to include this requirement in Laravel Roadmap ?