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

Added Hayagriva YAML export #10451

Merged
merged 5 commits into from
Oct 19, 2023
Merged

Conversation

JawadTUE
Copy link
Contributor

@JawadTUE JawadTUE commented Oct 6, 2023

Fixes #10382

I added Hayagrive YAML export based on their documentation.

The following fields are not included, because I did not find a relevant field for them in Jabref: parent, affiliated, issue, volume-total, page-total, time-range, runtime, serial-number, language, archive, archive-location.

HayagrivaType.java contains the mapping from Jabref type to Hayagriva Entry Type.

I confirmed that the exported .yaml file works with the typst system by using hayagriva literature.yml reference as stated in their documentation.

screenshot

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.

@Siedlerchr
Copy link
Member

Siedlerchr commented Oct 6, 2023

I think this looks already good. However, I think it's not necessary to have the own author formatter as they say they can be specified either in square brackets or in verbose mode with multiple authors under each other:

\begin{author}
author:
- literal: "\author"
\end{author}

could be reused here as well? (except the "literal")

Edit// Parent could refer to the crossref (e.g. inbook -> book) field in JabRef, but I don't know if or how this can be used in layouts. I would leave this out.

@Siedlerchr
Copy link
Member

Can you also please add a test for this? See the YamlExporterTest as an example

@Siedlerchr Siedlerchr added the status: changes required Pull requests that are not yet complete label Oct 12, 2023
@Siedlerchr
Copy link
Member

@JawadTUE How is the status here? Codewise it looked already good. Just unit tests missing

@JawadTUE
Copy link
Contributor Author

I will finish this by tomorrow.

@JawadTUE
Copy link
Contributor Author

I added the unit tests. These are basically the same as the tests in YamlExporterTest.java, with one extra test exportsCorrectMultipleAuthors to test that multiple authors are correctly exported.

@JawadTUE JawadTUE marked this pull request as ready for review October 16, 2023 18:51
@Siedlerchr Siedlerchr added status: ready-for-review Pull Requests that are ready to be reviewed by the maintainers and removed status: changes required Pull requests that are not yet complete labels Oct 18, 2023
@Siedlerchr Siedlerchr added this pull request to the merge queue Oct 19, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Oct 19, 2023
@Siedlerchr Siedlerchr added this pull request to the merge queue Oct 19, 2023
Merged via the queue into JabRef:main with commit b6d8f82 Oct 19, 2023
14 checks passed
@JawadTUE JawadTUE deleted the fix-for-issue-10382 branch October 28, 2023 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
export / save 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.

Typst-flavored (Hayagriva) YAML export
3 participants