Open xulman opened 4 days ago
I have of course forgotten to suggest what to do with it:
replace current code with
private Consumer<String> containerPathUpdateCallback = s -> {};
@xulman I agree, if you're interested in doing this, I would happily accept a PR, otherwise I'll get to it eventually.
actually, the PR #96 is solving this issue (by getting access to the original code base rather than trying to construct and use the dialog itself directly)
Minimal opening example
When working with the pointed at file/path, the dialog is calling its
containerPathUpdateCallback
, which is normally initiated asnull
.So, one has to provide there simply anything... to avoid having it getting NPE. And the issue is that it is not obvious and perhaps the empty callback could be a better initial setting than just null. What do you think? @bogovicj