When previewing an importer's results, there is a text field to enter the project name. When pressing Enter in this field, I would expect the project to be created (without having to click the "Create Project" button).

Agree. The current Enter key binding to the Update Preview button is not needed... since all the options on importer are bound to the Update Preview already, I think? Instead, hitting Enter key for the Create Project flow makes more sense.
Hey. I would like to work on this issue. Can someone please give me an abstract idea of where I can find the code relating to this issue?
I can tell you my method to find it:
grep but you can do it with all sorts of other tools (your IDE, for instance): grep -R "Create Project" ../main/webapp/modules/core/langs/translation-en.json: "core-buttons/create-project": "Create Project »", - that is the string you see in the screenshot! Unfortunately it is not input directly in the relevant JS/HTML code, but in a translation file instead. That is not a problem: we can keep searching using the translation identifier core-buttons/create-project.grep -R "core-buttons/create-project" ., and I find: ./main/webapp/modules/core/scripts/index/default-importing-controller/parsing-panel.js: this._parsingPanelElmts.nextButton.html($.i18n('core-buttons/create-project'));. That is the Javascript file we are looking for!With this technique you should be able to find your way in quite a lot of code bases, not just OpenRefine's.
Oh this is so helpful and smart trick. Thank You for explaining in such details.
I will be solving this issue now.
hi @wetneb , I am working on this issue, can you please assign me?
Hi @wetneb , can you please review the PR linked ?
Most helpful comment
I can tell you my method to find it:
grepbut you can do it with all sorts of other tools (your IDE, for instance):grep -R "Create Project" ../main/webapp/modules/core/langs/translation-en.json: "core-buttons/create-project": "Create Project »",- that is the string you see in the screenshot! Unfortunately it is not input directly in the relevant JS/HTML code, but in a translation file instead. That is not a problem: we can keep searching using the translation identifiercore-buttons/create-project.grep -R "core-buttons/create-project" ., and I find:./main/webapp/modules/core/scripts/index/default-importing-controller/parsing-panel.js: this._parsingPanelElmts.nextButton.html($.i18n('core-buttons/create-project'));. That is the Javascript file we are looking for!With this technique you should be able to find your way in quite a lot of code bases, not just OpenRefine's.