Skip to content

Conversation

@tobiasdiez
Copy link
Member

@tobiasdiez tobiasdiez commented Feb 23, 2019

Fixes #4614

Removes the resolve duplicate keys dialog. This feature is made obsolete by the integrity check and the user can generate new keys very simply (for all entries or only for the duplicated ones) through the entry editor and/or menu.


  • Change in CHANGELOG.md described
  • Tests created for changes
  • Manually tested changed features in running JabRef
  • Screenshots added in PR description (for bigger UI changes)
  • Ensured that the git commit message is a good one
  • Check documentation status (Issue created for outdated help page at help.jabref.org?)

@tobiasdiez tobiasdiez added the status: ready-for-review Pull Requests that are ready to be reviewed by the maintainers label Feb 23, 2019
@Siedlerchr
Copy link
Member

Well, however on import there should be a warning and the option to resolve duplicate keys. It's essential to discover duplicates

@tobiasdiez
Copy link
Member Author

tobiasdiez commented Feb 23, 2019

@Siedlerchr such a feature wasn't implemented (the only check was when opening a database) and is obsolete with my other PR #4692, where now keys are automatically generated for every imported entry. Duplicate entries are also highlighted in the import dialog.

@Siedlerchr
Copy link
Member

Okay, then I see no problem!

@Siedlerchr Siedlerchr merged commit 4deb581 into master Feb 23, 2019
@Siedlerchr Siedlerchr deleted the removeDuplicateKeyDialog branch February 23, 2019 16:49
Siedlerchr added a commit that referenced this pull request Feb 24, 2019
…tofx

* upstream/master:
  Catch NumberFormatException in BibTeXML exporter (#4698)
  Remove resolve duplicate keys dialog (#4696)
  fixes #4610. Changed the way the GroupDialog description is displayed.  (#4660)
  Bump slf4j-api from 1.8.0-beta2 to 1.8.0-beta4 (#4675)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: ready-for-review Pull Requests that are ready to be reviewed by the maintainers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

BibTexKey Duplicate Check throws NPE

3 participants