-
Notifications
You must be signed in to change notification settings - Fork 343
multi language open tasks #2315
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
base: develop
Are you sure you want to change the base?
Conversation
|
languages/multi-language/src/main/java/de/jplag/multilang/MultiLanguageParser.java
Outdated
Show resolved
Hide resolved
} | ||
|
||
public List<Token> parseFiles(Set<File> files, boolean normalize) throws ParsingException { | ||
this.printWarning(); | ||
List<Token> results = new ArrayList<>(); | ||
for (File file : files) { | ||
Optional<Language> language = findLanguageForFile(file); |
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.
We discussed that we can find out at compile time whether the mapping of file extensions to language modules is well-defined. I would argue then that we should set up an actual look up table instead of repeating the same steps for each individual file.
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.
This is not a specific warning, but a general one that is printed the first time the language module is used. See #2304
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 someone wants to use the content and not only the file extensions: https://github.com/ArDoCo/magika we ported magika to java :)
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.
We could do that, but I'd recommend doing it in a separate PR and everywhere in JPlag
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.
Yes, I meant it as general information . I would not implement it in this PR :)
Fixes the open tasks from #2304