Skip to content
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

Extract calls to JabRefFrame and substitute with LibraryTabContainer #10724

Merged
merged 33 commits into from
Jan 2, 2024

Conversation

calixtus
Copy link
Member

Mandatory checks

  • Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)
  • Tests created for changes (if applicable)
  • Manually tested changed features in running JabRef (always required)
  • Screenshots added in PR description (for UI changes)
  • Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
  • Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

@calixtus calixtus added status: ready-for-review Pull Requests that are ready to be reviewed by the maintainers dev: code-quality Issues related to code or architecture decisions labels Dec 25, 2023
Copy link
Member

@koppor koppor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small comments.

Copy link
Contributor

github-actions bot commented Dec 30, 2023

The build for this PR is no longer available. Please visit https://builds.jabref.org/main/ for the latest build.

Copy link
Member

@tobiasdiez tobiasdiez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not enough time right now for a full review, but based on a cursory glance it looks good to me.

Happy new year!

}

frame.getCurrentLibraryTab().markBaseChanged();
tabSupplier.get().markBaseChanged();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like most of the remaining usages of the LibraryTab are now related to the "changed" status. Is it easy to push this down to the database context (as a follow-up of course)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll see. My plan is to somehow really fix the undo redo stuff and for that I want to utilize the commands we're using and maybe putting them eventually on a reactive stream. But there is still some road to walk.
Upmost next is some refactoring of libraryTab and jabrefframe

@koppor koppor added this pull request to the merge queue Jan 2, 2024
Merged via the queue into main with commit 10394d2 Jan 2, 2024
@koppor koppor deleted the extract-frame branch January 2, 2024 08:28
Siedlerchr added a commit that referenced this pull request Jan 2, 2024
* upstream/main:
  Adds three tests to verify the expected output from the getErroMessage function. The tests check the output message when ParserResult is empty, not empty, or has duplicates. (#10711)
  Extract calls to JabRefFrame and substitute with LibraryTabContainer (#10724)
Siedlerchr added a commit that referenced this pull request Jan 3, 2024
* 'main' of github.com:JabRef/jabref:
  Ignore 429 at link check (#10743)
  Fix color for hovered special fields (#10742)
  Adds three tests to verify the expected output from the getErroMessage function. The tests check the output message when ParserResult is empty, not empty, or has duplicates. (#10711)
  Extract calls to JabRefFrame and substitute with LibraryTabContainer (#10724)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev: code-quality Issues related to code or architecture decisions 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.

3 participants