You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If missing account type filter is an oversight, then when assuming it is optional it could be fixed by adding a conditional addon onto the already existing queryable object (see bellow comment):
However, if the "Account Type" search parameter is not needed, then it needs to be removed from the Gateway signature, Use Case signature & their interfaces, as well as from Controller parameters and its XML documentation. Depending on how well this API is tested, the tests might need to change as well.
The text was updated successfully, but these errors were encountered:
Problem:
Get All (Accounts)
endpoint's Gateway does not make use of providedAccount Type
parameter when filtering entities (see bellow), ...account-api/AccountsApi/V1/Gateways/AccountApiGateway.cs
Lines 38 to 49 in 069bfa1
... while it is specified as available, active parameter on the endpoint controller's xml comment documentation (see Line 82):
account-api/AccountsApi/V1/Controllers/AccountApiController.cs
Lines 78 to 92 in 069bfa1
Potential Solution:
The text was updated successfully, but these errors were encountered: