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
Many of the internal classes, e.g. Jdbi3ErrorContext and SimpleErrorContext, have a lot (11) of constructor parameters. The utility methods in ErrorContextUtilities also have a fair number of arguments, though not nearly as many, which come from the set of constructor parameters to the context classes.
These options should be factored into a separate (internal for now) class which can be supplied to constructors and methods. This will both simplify the code, and provide a single location where any new options can be added without impacting existing code that uses them.
The text was updated successfully, but these errors were encountered:
Note specifically that NO public APIs are affected.
* Introduce ErrorContextOptions class
* Refactor code to use the options class instead of large argument lists
* Add Checker Nullable annotation to methods in ErrorContextUtilities
Closes#300
)
Note specifically that NO public APIs are affected.
* Introduce ErrorContextOptions class
* Refactor code to use the options class instead of large argument lists
* Add Checker Nullable annotation to methods in ErrorContextUtilities
Closes#300
Many of the internal classes, e.g.
Jdbi3ErrorContext
andSimpleErrorContext
, have a lot (11) of constructor parameters. The utility methods inErrorContextUtilities
also have a fair number of arguments, though not nearly as many, which come from the set of constructor parameters to the context classes.These options should be factored into a separate (internal for now) class which can be supplied to constructors and methods. This will both simplify the code, and provide a single location where any new options can be added without impacting existing code that uses them.
The text was updated successfully, but these errors were encountered: