Closed
Description
Mariusz Mączkowski opened DATACMNS-1304 and commented
Uppercase letters at the end of property are cutted now what is inconsistent with finding the longest property name first.
Example:
interface Product {
...
Category getCategoryB(); // contains single uppercase letter at the end
Category getCategoryAB(); // contains uppercase letters at the end
}
interface Category {
Long getId();
...
}
In this case, parsing method names
findByCategoryBId
and
findByCategoryABId
causing an exception.
Affects: 2.1 M2 (Lovelace), 1.13.12 (Ingalls SR12), 2.0.7 (Kay SR7)
Issue Links:
- DATACMNS-1570 Parsing of query method names is inconsistent for attributes beginning with a single lower case character followed by an upper case character
Referenced from: pull request #289
Backported to: 2.0.8 (Kay SR8), 1.13.13 (Ingalls SR13)