Repository navigation
Conversation
…tribute of that name
…an attribute filter
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The ResourceDoc of
GET /obp/v7.0.0/banks/BANK_ID/customersnow states that every query parameter other than the paging and date names is an attribute filter, so a misspelt name is not refused:?limt=10asks for Customers with an attributelimtwhose value is10, which usually returns an empty list rather than an error, and the doc tells callers to check the spelling of limit, offset and sort_direction when a call returns no Customers. A new scenario inCustomersAtOneBankV700Testpins this behaviour, with and without another filter.