GUI for consistency check#12433
Conversation
There was a problem hiding this comment.
JUnit tests are failing. In the area "Some checks were not successful", locate "Tests / Unit tests (pull_request)" and click on "Details". This brings you to the test output.
You can then run these tests in IntelliJ to reproduce the failing tests locally. We offer a quick test running howto in the section Final build system checks in our setup guide.
Recording.2025-01-31.mp4Added a table, but figuring out how to proceed with inserting data into the table as shown in the UI. Please review. |
There was a problem hiding this comment.
JUnit tests are failing. In the area "Some checks were not successful", locate "Tests / Unit tests (pull_request)" and click on "Details". This brings you to the test output.
You can then run these tests in IntelliJ to reproduce the failing tests locally. We offer a quick test running howto in the section Final build system checks in our setup guide.
calixtus
left a comment
There was a problem hiding this comment.
Just by a quick look two remarks
Also about the picture in the issue: The user needs some hints what o and ? and so on mean. It must be understandable somehow right away.
There was a problem hiding this comment.
Your code currently does not meet JabRef's code guidelines.
We use Checkstyle to identify issues.
Please carefully follow the setup guide for the codestyle.
Afterwards, please run checkstyle locally and fix the issues.
In case of issues with the import order, double check that you activated Auto Import.
You can trigger fixing imports by pressing Ctrl+Alt+O to trigger Optimize Imports.
5b9e279 to
09251a8
Compare
Co-authored-by: Houssem Nasri <housi.housi2015@gmail.com>
…95/jabref into consistencyGuiCheck
|
I have taken a lot of code as it is from the |
Recording.2025-02-03.mp4The table is displaying data correctly. What remains to be done:
|
|
Either i dont understand one comment or its an artifact from another pr? |
|
Everything else looks good to go. Thanks for your great addition! |
Head branch was pushed to by a user without write access
| @Override | ||
| public String toString() { | ||
| return "[" + message() + "]"; | ||
| } |
There was a problem hiding this comment.
This is redundant here, as records provide a built-in toString method.
The purpose of this method elsewhere in the codebase is when multiple fields are required, like "[ " + bibEntry.getCitationKey() + ", " + message.toString() + " ]". However, the message field itself already includes the citationKey.
jabref/src/main/java/org/jabref/logic/integrity/IntegrityMessage.java
Lines 11 to 14 in 39d7971
In the follow up PR, should I also remove this.
|
@priyanshu16095 Thank you for the work on this - would you feel comfortable to write a blog entry for this? (JabRef/blog.jabref.org#108) - I think, you have enough domain knowledge to explain? In your screenshot, I saw that there is the column "Pages" filled with "O". That should not happen - if everything is the same (presence), then there should be no output - or is the logic different. Finally, the logic of the consistency check maybe should ignore JabRef's fields (ranking in your example). That can be a follow-up. Maybe even configurable during the check itself? |
|
Sure! I'd be happy to write a blog entry for this. I'll check why the "Pages" column is showing "o" and adjust the logic if needed. Ignoring JabRef-specific fields in the consistency check sounds like a good idea. I'll definitely try it in a follow-up. |
Nice! In parallel, I would ask for a text for https://github.com/JabRef/user-documentation. I think, there is an overlap of 80% 😅 (Which is OK!). The blog won't evolve later, but the user documention 😅 |
|
Understood! I’ll ensure the core content fits both needs. |
|
Follow-up issue: #12695 |
|
Follow-up issue #12696 |
|
Follow-up issue: #12697 Sorry for the many follow-up isuses. I was so happy to see this in, but did not thouroughly test it. |
|
Follow up: #12487 |
Fixes #11950
This PR introduces a GUI for a bibliography consistency check to ensure consistency among BibTeX entries.
Mandatory checks
CHANGELOG.mddescribed in a way that is understandable for the average user (if change is visible to the user)