-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OO Maintenance: Better checks, clean up dead code, refactoring #11779
Conversation
@@ -601,12 +587,12 @@ private boolean checkThatEntriesHaveKeys(List<BibEntry> entries) { | |||
Optional<BibDatabaseContext> databaseContext = stateManager.getActiveDatabase(); | |||
if (citePressed && databaseContext.isPresent()) { | |||
// Generate keys | |||
CitationKeyPatternPreferences prefs = preferences.getCitationKeyPatternPreferences(); | |||
CitationKeyPatternPreferences citationKeyPatternPreferences = preferences.getCitationKeyPatternPreferences(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe, you can have these passed in the constructor - and get rid of preferences
parameter alltogheter? ^^
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be the ideal level of abstraction, but preferences
would be needed here:
Reason for moving openOfficePreferences
in the constructor initialization block was that it is the core preference used all over the class (22 usages), whereas the rest of the preferences (ExternalApplicationsPreferences
, LayoutFormatterPreferences
, CitationKeyPatternPreferences
) are used just used once in within their respective scopes (three times all together in total), thus declared locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@koppor I tried to clean it up a bit further by passing all the preference subtypes via constructor. Although I couldn't get rid of preferences
, I could minimize its usage to this one place (above comment). Check commit f759087. If this is not useful, we can revert the commit.
Advantage (imo) - more inversion of control (gets rid of all getters).
Ping: @calixtus
@@ -511,12 +511,6 @@ private void pushEntries(CitationType citationType, boolean addPageInfo) { | |||
} | |||
|
|||
final BibDatabaseContext bibDatabaseContext = stateManager.getActiveDatabase().get(); | |||
if (bibDatabaseContext == null) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Future: It is ok to add assert
statements.
Example:
assert bibDatabaseContext != null
OK, one needs to add -ea
somehow: https://stackoverflow.com/a/18168305/873282 -- I would have bet that I saw assertion errors when developing...
The long discussion at https://stackoverflow.com/q/2758224/873282 says: do something else, but I like assertions:
- More semantic meaning than removed code
- More semantic meaning than code comments
- Runs in debug mode only (in contrast to
Objects.requireNonNull
- Does not clutter the code with
@NonNull
annotations, which need a separate framework for checking - (https://github.com/kelloggm/checkerframework-gradle-plugin)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, will follow that.
Reason for removal here was that bibDatabaseContext
could never be null here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure. At the time of the code. But what if there is a future refactoring. One could argue that the whole research of pre- and post conditions is useless, because the author was sure at when writing the code 🤣🤣
This kind of code (or JSpecify annitations are useful for working on the code at a later point of time. To avoid regressions.
Side track: Another tool for avoiding regressions is OpenFastTrace - see https://devdocs.jabref.org/requirements/ for details ^^.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it is to ensure the precondition, it is better to revert this change and use the dedicated error dialog instead of using an internal assertion. Will be updated in latest commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checks for empty database and databasecontext merged in (updated) lines 509-515.
boolean hasStyle = true; // (style != null); | ||
boolean hasDatabase = true; // !getBaseList().isEmpty(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two comments (non-null check / isEmpty) are typical assert
statements.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay wait, don't merge yet, I'll see if I can put those conditions/assertions (replacing style
->currentStyle
) instead of complete removal. I don't know if there were reasons these were commented and true was hardcoded.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed: use of assert
form my point of view okay now |
I'll try to finish this up by tomorrow. Not much left. Just checking if we can work without listeners (I did something similar when disabling buttons during the csl project)...or else just add a few assertions. |
Whenever available, I request one of you to check the diff since the last changes and give an approval for merge. |
true
/false
.preferences
by passing specific preferences via constructor.Mandatory checks
CHANGELOG.md
described in a way that is understandable for the average user (if applicable)