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
Uppercase letters at the end of property are cutted now what is inconsistent with finding the longest property name first.
Example:
interfaceProduct {
...
CategorygetCategoryB(); // contains single uppercase letter at the endCategorygetCategoryAB(); // contains uppercase letters at the end
}
interfaceCategory {
LonggetId();
...
}
DATACMNS-1570 Parsing of query method names is inconsistent for attributes beginning with a single lower case character followed by an upper case character
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:
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:
Referenced from: pull request #289
Backported to: 2.0.8 (Kay SR8), 1.13.13 (Ingalls SR13)
The text was updated successfully, but these errors were encountered: