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
Code mining parameters are skipped when the passed parameter name is a substring of the passed parameter. For example,
public void foo(int a, int b, int c) {
}
public void foo2(int abc) {
foo(abc, abc, abc); <== this line will show no parameter names because a, b, and c can be found in all the parameter names
}
The parameter name should only be dropped if it is an exact/lower-case match. An option can be added to filter out partial name matches.
The text was updated successfully, but these errors were encountered:
- add two new preferences regarding the default filter and the
filtering of implied parameter names
- for filtering of implied parameter names, do not filter out
parameter names that are 3 characters or less that are contained
in the argument but filter them out if they are equal
- bump up jdt.ui minor version as new preference constants are added
- fixeseclipse-jdt#1437
- add two new preferences regarding the default filter and the
filtering of implied parameter names
- for filtering of implied parameter names, do not filter out
parameter names that are 3 characters or less that are contained
in the argument but filter them out if they are equal
- bump up jdt.ui minor version as new preference constants are added
- fixes#1437
Code mining parameters are skipped when the passed parameter name is a substring of the passed parameter. For example,
The parameter name should only be dropped if it is an exact/lower-case match. An option can be added to filter out partial name matches.
The text was updated successfully, but these errors were encountered: