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
This is a bug - we need to use the correct parameter name.
For the analysis factories, using the name of a local variable with the same name as the passed in dictionary key is really the best we can do.
NOTE: These factories were meant to be used with Java's Service Provider Interface, which is a service locator that is built-into Java. So, that basically makes them a poor fit for DI methods in .NET. We are considering options for how to deal with these using proper constructor parameters rather than passing in dictionaries and doing a bunch of casting.
The text was updated successfully, but these errors were encountered:
#682 (#1033)
This addresses a few incorrect usages of various argument exceptions, such as missing/incorrect parameter names, using ArgumentOutOfRangeException with a parameter name that doesn't exist, missing messages for ArgumentException, and so on.
For the analysis factories, these were reverted to be ArgumentException because various analysis tools (including Sonar and ReSharper/Rider) complain about using a key name for the dictionary when it doesn't exist as a parameter.
Mentioned in #648
Issues found: https://sonarcloud.io/project/issues?resolved=false&rules=csharpsquid%3AS3928&id=apache_lucenenet
This is a bug - we need to use the correct parameter name.
For the analysis factories, using the name of a local variable with the same name as the passed in dictionary key is really the best we can do.
The text was updated successfully, but these errors were encountered: