-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Migrate fetchers to Search.g4 ANTLR parser. #13691
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
Conversation
-Changed inherited fetcher classes to use ANTLR generated classes instead of lucene libraries. - Changed ACMPortalFetcher.java logic for transforming the parsed syntax to URL
jablib/src/main/java/org/jabref/logic/importer/fetcher/ACMPortalFetcher.java
Outdated
Show resolved
Hide resolved
Great start, to me it looks like your on the right track. |
- Changed ACMPortalFetcherTest unit test code to use Search.g4 generated classes instead of Lucene - Removed trivial comment from ACMPortalFetcher
- Changed AbstractQueryTransformer methods to obey Search.g4 parser rules - Modified ACMPortalFetcher to use the changed transformer logic
…d the search based fetcher classes to use it
…de while still being compatible with Search.g4 parser
jablib/src/main/java/org/jabref/logic/importer/SearchBasedFetcher.java
Outdated
Show resolved
Hide resolved
jablib/src/test/java/org/jabref/logic/importer/fetcher/ArXivFetcherTest.java
Show resolved
Hide resolved
jablib/src/test/java/org/jabref/logic/importer/fetcher/BvbFetcherTest.java
Show resolved
Hide resolved
jablib/src/test/java/org/jabref/logic/importer/fetcher/DOABFetcherTest.java
Show resolved
Hide resolved
… new parser and node logic
…the new Search.g4 logic. Fixed how AbstractQueryTransformer handles fields.
jablib/src/main/java/org/jabref/logic/importer/fetcher/INSPIREFetcher.java
Show resolved
Hide resolved
jablib/src/main/java/org/jabref/logic/importer/fetcher/JstorFetcher.java
Show resolved
Hide resolved
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.
cool thanks for the work on this!
What about the todos in the PR, are they addressed? Do you plan to address them now or in a follow up? |
@trag-bot didn't find any issues in the code! ✅✨ |
Documentation issue is JabRef/user-documentation#584 |
Tested it, works fine. ❤️ |
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.
Thank you very much for this PR. Yes it was a lot of work and a hell of a ride through the search subsystem, but I hope it was worth it for you. It is a great addition to our codebase and we appreciate it very much!
I had added them when I opened the pr request as a draft and when the work was incomplete, they are done. |
Thank you! I really appreciate you saying that. It was definitely a challenge but I think it gave me valuable experience. |
The task was not completely described. The query validator on the UI seems to use a different validation. ![]() @turhantolgaunal Do you think, you can take care of this? |
Ok, I will look into it |
Closes #13607
TO DO:
Steps to test
Using the Search.g4 syntax for searching on the web with different options.
Documentation issue JabRef/user-documentation#584
Mandatory checks
CHANGELOG.md
described in a way that is understandable for the average user (if change is visible to the user)