16075 support multiple customized preview styles by bgyoo970 · Pull Request #16615 · JabRef/jabref

bgyoo970 · 2026-08-17T22:47:26Z

Summary

 The available panel was split into the 'CSL' and 'Customized' tabs to display preset or customized preview layouts respectively. Buttons were added to support the addition and deletion of specifically custom styles under the 'customized' tab only, along with a text box to rename customized styles. Changes were made throughout related files to support more than just the one default "PREVIEW" custom layout and persist multiple custom layouts between user sessions.

Related to issue 16075
Closed Previous PR, due to merge from main

Analogies

 New to the code, progress flows like honey
 Straightforward as chocolate, good first grab
 Helpful resources and references on the money
 Added custom changes through views, buttons, and tabs
 This was more fun as a poem, instead of a paragraph
 Something, something, a rhyme about the moon
 I wish I had more analogies for a good laugh
 but it's getting late, and I should sleep soon
    `jabref-contrib-policy:4.2:reviewed:ok`

Steps to test

Describe how reviewers can test this fix/feature.
Ideally, think of how you would guide a beginner user of JabRef to try out your change.

A. Add Custom Layout: Options → Preferences → Entry preview → Customized Tab → '+' (add button)
Upon opening the Entry Preview under preferences, navigate to the 'Available' Panel and click on the 'Customized' tab. There you will see a '+' plus button and a '-' minus button. Click on the plus button and you should see a new customized style appear under the 'Customized' tab.

B. Delete Custom Layout: Options → Preferences → Entry preview → Customized Tab → '-' (minus button)
Similarly from adding a custom layout, under the 'Customized' tab in the 'Available' Panel, you will see a '-' minus button. This button will be greyed out until you select a custom style under the 'Customized' tab. If none exist, create one using the '+' plus button. Then select the desired custom style to delete. The minus button will be available to click on. Click on the minus button and you will see that the custom style gets removed from the list.

C. Rename Custom Layout: Options → Preferences → Entry preview → Customized Tab → Under this tab, select custom style to rename → 'Name' text box -> Type name → Hit 'Enter'
Upon opening the Entry Preview under preferences, navigate to the 'Customized' tab or the 'Selected' Panel and click on a custom style. There, you should see at the bottom right corner of the UI, a text field with the name of your custom style. Rename your style as needed and hit 'Enter' to confirm the change. Note you may only rename custom styles. These custom styles will exist under the 'Selected' Panel or under the 'Customized' Tab. Duplicate names are not allowed.

D. Persisted Custom Layouts: After making changes to the 'Customized' tab's contents, Save your changes with the button at the bottom of the UI. Then re-navigate to the Entry Preview UI's 'Customized' tab and confirm that the changes have persisted. This will persist all data around the custom layouts around moving, renaming, adding, deleting, and editing layout's text.
Add screenshots (preferred) or videos.

entryeditor-preview-settings-customized-tab

Related issues and pull requests

Closes #16075

AI usage

Claude (Sonnet 5) was used to assist in understanding the code and providing feedback or suggestions to my approaches. I understand the feedback it provided and had it review each step of the CHECKLIST.md. Adjustments were made as needed after reviewing the checklist, while running successful verification steps and unit tests afterwards.

AI CHECKLIST.md walkthrough

Nullability and control flow

No == null/!= null in this PR's changes.
No Objects.requireNonNull(...).
New classes @NullMarked (CustomizedPreviewStyle).
Optional consumed via map/flatMap/orElseThrow, never orElse(unusedValue) — PreviewLayout.of now returns Optional end to end, and ClipboardContentGenerator's orElse(...) supplies a genuine fallback value.
StringUtil.isBlank(...) used correctly.

Exceptions

No bare catch (Exception e).
No RuntimeException/IllegalStateException.
Logged exceptions passed as the last logger argument.

Style and idioms

New BibEntry objects built with withers — not applicable, no BibEntry construction in this change.
Modern Java used: List.of(), UUID, SequencedCollection, etc.
Regexes use a precompiled Pattern.compile(...) constant — not applicable, no new regexes introduced.
Background work uses BackgroundTask, not new Thread() — not applicable, no new background work introduced.
No commented-out code, no trivial comments restating the code, no AI-disclosure comments in source.
Markdown Javadoc (///) uses Markdown syntax, not JavaDoc inline tags, in new/changed doc comments.

User-facing text

All user-facing text localized (Localization.lang in Java, % prefix in FXML).
Sentence case (not Title Case); no trailing !; labels do not end with :.
Variance expressed with placeholders ("...: %0"), not string concatenation — not applicable, no new strings in this change interpolate variable content.

Security

User-controlled data HTML-escaped before being written into any text/html response — not applicable, no HTML response rendering in this change.

Tests

Behavior changes in org.jabref.model / org.jabref.logic have added or updated tests.
Tests assert object contents (assertEquals), use plain JUnit asserts (not AssertJ), have no @DisplayName, do not catch exceptions, and use @tempdir instead of manual temp directories — no manual temp-directory usage introduced, so the @tempdir clause is not applicable here.

2. Verification commands

Run in this order — cheapest first. Each must pass.

./gradlew :jablib:check (or ./gradlew check for all modules).
./gradlew checkstyleMain checkstyleTest checkstyleJmh.
./gradlew modernizer.
./gradlew --no-configuration-cache :rewriteDryRun reports no changes.
./gradlew javadoc.
npx markdownlint-cli2 "docs/**/.md" ".md" — run, since entry-preview.md was added.
[/] IntelliJ-format Docker step — not needed; rewriteDryRun reported clean.

3. Documentation

CHANGELOG.md entry added.
Searched jabref/issues and jabref-koppor/issues for a related issue.
Requirement added to docs/requirements/entry-preview.md.
[/] Developer documentation under docs/ updated — not applicable, no architecture/dev docs describe this subsystem.

4. Pull request

PR body built from .github/PULL_REQUEST_TEMPLATE.md, every section filled.
All checklist items kept and marked [x], [ ], or [/].
All HTML comments removed from the PR body.
PR created (via the GitHub website; equivalent in effect to gh pr create --body-file — no CLI-specific escaping concern applies since the body was entered directly, not piped through a shell command).
CHANGELOG.md linked a real issue from the start — no TODO placeholder was used, so there's nothing to swap out post-creation.

Checklist

I own the copyright of the code submitted and I license it under the MIT license
If AI tools were used, I disclosed them in the "AI usage" section and reviewed, understood, and take full ownership of all AI-generated code
I manually tested my changes in running JabRef (always required)
I added JUnit tests for changes (if applicable)
I added screenshots in the PR description (if change is visible to the user)
I added one sentence (max 20 words) to CHANGELOG.md describing the change from the user's point of view (if change is visible to the user)
I checked the user documentation for up to dateness and submitted a pull request to our user documentation repository

…ation style, Split 'available' panel into csl and customized tabs. customized styles show in editor preview panel, renaming functionality added, add and delete button added to customized tab to add/delete customized styles, persistence added to preserve customized styles and renamings

Merge changes into forked main branch

… constants to jabref_en.properties, refactored naming for CustomizedPreviewStyle

…d string constants to jabref_en.properties, refactored naming for CustomizedPreviewStyle" This reverts commit 9d11263.

…last commit, minus changes to abbrv.jabref.org and csl-styles

…clature

…comments and null checks. used modern Java for factory instead of constructor. updated string in JabRef_en.properties. updated changelog and created entry-preivew.md with new features.

…view-styles

…ple-customized-preview-styles

…ss Localization.lang concat violation, resolved NPE risk on TextBasedPreviewLayout constructor, resolve legacy migration rerun on empty list, updated previewPreferences to use CUID over legacy name, fixed rename test case for null pass, removed dependency on javafx.swing, changing out of main branch, updated doc feature req descriptions

…view-styles

qodo-free-for-open-source-projects · 2026-08-17T22:48:30Z

PR Summary by Qodo

Support multiple customized entry preview styles

✨ Enhancement 🧪 Tests 📝 Documentation 🕐 40+ Minutes

AI Description

• Split Entry Preview “Available” list into “CSL” and “Customized” tabs.
• Add create/delete/rename UX for custom preview styles (customized tab only).
• Persist multiple custom styles by stable IDs, including legacy migration and tests.

Diagram

graph TD
  A["Preview settings UI"] --> B["PreviewTab"] --> C["PreviewTabViewModel"] --> D["PreviewPreferences"] --> E["JabRefGuiPreferences store"] --> F["PreviewLayout.of(...)" ] --> G["TextBasedPreviewLayout"]
  F["PreviewLayout.of(...)" ] --> H["CSL/BST layouts"]
  C["PreviewTabViewModel"] --> I["CustomizedPreviewStyle (record)"]
  subgraph Legend
    direction LR
    _ui["UI"] ~~~ _vm["ViewModel"] ~~~ _pref[("Preferences")] ~~~ _model["Model/Logic"]
  end

High-Level Assessment

The following are alternative approaches to this PR:

1. Store custom styles as a single JSON blob preference

➕ Atomic read/write avoids partial-series corruption across ID/name/text keys
➕ Simplifies migration logic (one key instead of three numbered series)
➕ Easier to evolve schema (add fields like 'createdAt', 'lastUsed')
➖ Requires JSON parsing/serialization dependency or custom codec
➖ Harder to manually inspect/edit preferences compared to simple key series

2. Persist via existing JabRef preference list serialization utilities

➕ Reuses established patterns for list persistence and reduces custom code
➕ Potentially fewer edge cases around purging trailing keys
➖ May not support multi-field records (id/name/text) without additional encoding
➖ Still needs careful handling of newline escaping and backward compatibility

Recommendation: The chosen approach (stable IDs + explicit migration + Optional-based layout resolution) is directionally correct for rename-safe persistence and multi-style support. If future iterations expand the record schema, consider consolidating the three numbered key-series into a single structured value (e.g., JSON) to make persistence atomic and reduce partial-write edge cases; otherwise the current implementation is acceptable given the added tests and explicit purge/migration safeguards.

Files changed (15) +1440 / -159

Enhancement (6) +573 / -131

JabRefGuiPreferences.javaPersist multiple customized preview styles with legacy migration +100/-26

Persist multiple customized preview styles with legacy migration

• Replaces the single PREVIEW_STYLE string with a list of persisted custom styles (id/name/text) stored as numbered key series. Adds one-time migration from the legacy PREVIEW_STYLE key, newline encoding/decoding, and updates layout-cycle rebuilding to resolve custom layouts by ID via Optional-returning PreviewLayout.of().

jabgui/src/main/java/org/jabref/gui/preferences/JabRefGuiPreferences.java

PreviewTab.javaSplit Available list into tabs and add custom style add/delete/rename UI +169/-25

Split Available list into tabs and add custom style add/delete/rename UI

• Reworks the JavaFX preferences tab to show 'CSL' vs 'Customized' available styles, adds +/- buttons for custom styles, and adds a name TextField bound to the ViewModel for renaming. Updates drag/drop and move-button behavior to route items between the correct source/destination lists and to refocus tabs based on the last moved layout type.

jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTab.java

PreviewTabViewModel.javaIntroduce separate CSL/customized available lists and custom-style CRUD/rename +203/-54

Introduce separate CSL/customized available lists and custom-style CRUD/rename

• Splits the available list into cslListProperty and customizedListProperty, with shared filtering and routing logic based on layout type. Adds creation/deletion of custom styles, rename validation (non-blank, no duplicates across both tabs), improved drag/drop handling, and persistence of all custom styles (chosen + customized) into PreviewPreferences as CustomizedPreviewStyle records.

jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTabViewModel.java

PreviewPreferences.javaReplace single custom preview layout string with list of customized styles +18/-22

Replace single custom preview layout string with list of customized styles
• Refactors PreviewPreferences to store an ObservableList of CustomizedPreviewStyle records. Updates defaults and selected-layout fallback behavior to derive text-based previews from the first stored custom style when the cycle is empty/invalid.
jabgui/src/main/java/org/jabref/gui/preview/PreviewPreferences.java

CustomizedPreviewStyle.javaIntroduce persisted record for custom preview styles +16/-0

Introduce persisted record for custom preview styles
• Adds a @NullMarked record holding (id, name, text) plus a convenience constructor generating a CUID-based ID to keep renames stable across sessions.
jablib/src/main/java/org/jabref/logic/preview/CustomizedPreviewStyle.java

TextBasedPreviewLayout.javaAdd stable ID and editable name to text-based preview layouts +67/-4

Add stable ID and editable name to text-based preview layouts
• Extends TextBasedPreviewLayout with an id and mutable name, adds constructors/factories for (id,name,text) creation, and updates display-name behavior to reflect user-defined names while preserving sensible fallbacks.
jablib/src/main/java/org/jabref/logic/preview/TextBasedPreviewLayout.java

Bug fix (1) +6 / -4

ClipboardContentGenerator.javaSelect a default custom preview layout from persisted custom styles +6/-4

Select a default custom preview layout from persisted custom styles
• Updates clipboard preview generation to use the first persisted CustomizedPreviewStyle as the fallback template (or a default placeholder when none exist) instead of the legacy single custom preview layout preference.
jabgui/src/main/java/org/jabref/gui/preview/ClipboardContentGenerator.java

Refactor (1) +20 / -24

PreviewLayout.javaResolve preview layouts by identifier via Optional and custom-style IDs +20/-24

Resolve preview layouts by identifier via Optional and custom-style IDs
• Changes PreviewLayout.of(...) to return Optional<PreviewLayout> and resolves text-based custom layouts by stable ID from a provided list of CustomizedPreviewStyle records. Keeps CSL and BST resolution paths while eliminating null returns.
jablib/src/main/java/org/jabref/logic/preview/PreviewLayout.java

Tests (4) +787 / -0

PreviewTabViewModelTest.javaAdd ViewModel tests for multi-custom-style behavior and routing +552/-0

Add ViewModel tests for multi-custom-style behavior and routing
• Adds comprehensive tests covering loading styles into the correct lists, persistence of all custom styles, defaulting behavior when lists are empty, add/remove/rename flows, and drag/drop routing and no-op behavior when dropping into the same list.
jabgui/src/test/java/org/jabref/gui/preferences/preview/PreviewTabViewModelTest.java

PreviewPreferencesTest.javaAdd PreviewPreferences tests for customized-style defaults and selection +92/-0

Add PreviewPreferences tests for customized-style defaults and selection
• Validates that defaults include exactly one default customized style and that getSelectedPreviewLayout falls back to the first customized style when the cycle is empty, while respecting populated cycles.
jabgui/src/test/java/org/jabref/gui/preview/PreviewPreferencesTest.java

PreviewLayoutTest.javaTest PreviewLayout factory resolution for customized styles by ID +65/-0

Test PreviewLayout factory resolution for customized styles by ID
• Adds tests ensuring PreviewLayout.of(...) resolves custom styles by ID (independent of display name) and returns empty Optional for unknown identifiers or empty custom-style lists.
jablib/src/test/java/org/jabref/logic/preview/PreviewLayoutTest.java

TextBasedPreviewLayoutTest.javaTest TextBasedPreviewLayout ID generation and constructor semantics +78/-0

Test TextBasedPreviewLayout ID generation and constructor semantics
• Adds tests confirming generated IDs are non-null/unique when appropriate, that provided IDs are preserved, and that Layout-based construction still yields a non-null ID via accessor behavior.
jablib/src/test/java/org/jabref/logic/preview/TextBasedPreviewLayoutTest.java

Documentation (3) +54 / -0

CHANGELOG.mdDocument multi-custom preview style support in changelog +1/-0

Document multi-custom preview style support in changelog
• Adds a user-facing changelog entry describing the new ability to create/manage/persist customized preview styles and the UI tab split.
CHANGELOG.md

entry-preview.mdAdd requirements doc for Entry Preview tab split and custom-style management +43/-0

Add requirements doc for Entry Preview tab split and custom-style management
• Introduces requirement statements for the CSL/Customized tabs, CRUD + rename behavior, and persistence by stable ID independent of display name.
docs/requirements/entry-preview.md

JabRef_en.propertiesLocalize new Entry Preview UI strings and rename validation messages +10/-0

Localize new Entry Preview UI strings and rename validation messages
• Adds localized strings for CSL/Customized tab titles, the style name field, and validation errors for duplicate/blank renames, plus a template for default custom-style naming.
jablib/src/main/resources/l10n/JabRef_en.properties

qodo-free-for-open-source-projects · 2026-08-17T22:52:57Z

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. setPreviewLayout(null) called ✓ Resolved 📘 Rule violation ≡ Correctness

Description

refreshPreview() clears state by passing null into setPreviewLayout, violating the
no-null-arguments rule and increasing risk of future NPEs at call sites. Use an explicit clear
method/Optional/property reset instead of a null argument.

Code

jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTabViewModel.java[R209-210]

+        PreviewLayout current = selectedLayoutProperty.getValue();
setPreviewLayout(null);
-        setPreviewLayout(chosenSelectionModelProperty.getValue().getSelectedItem());
-    }
-
-    private PreviewLayout findLayoutByName(String name) {
-        return availableListProperty.getValue().stream().filter(layout -> layout.getName().equals(name))
-                                    .findAny()
-                                    .orElse(chosenListProperty.getValue().stream().filter(layout -> layout.getName().equals(name))
-                                                              .findAny()
-                                                              .orElse(null));

Evidence
PR Compliance ID 18 forbids passing null as an argument in new/modified code. The changed method
refreshPreview() explicitly calls setPreviewLayout(null).
AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods): AGENTS.md: Do Not Pass Null as an Argument (Except to Same-Named Methods)
jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTabViewModel.java[208-212]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`PreviewTabViewModel.refreshPreview()` calls `setPreviewLayout(null)`, which violates the rule against passing `null` as an argument.
## Issue Context
`setPreviewLayout` already handles `null`, but the compliance requirement forbids introducing/using `null` arguments in new/modified code.
## Fix Focus Areas
- jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTabViewModel.java[208-212]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. ~~Custom cycle migration broken~~ ✓ Resolved 🐞 Bug ≡ Correctness

Description

Upgraded installations can lose the customized layout entry in the preview cycle because customized
layouts are now resolved only by id, while legacy PREVIEW_CYCLE values use the "PREVIEW" identifier
and the legacy migration generates a new random id. This can drop the customized layout from the
reconstructed cycle and reset the selected preview style after upgrade.

Code

jablib/src/main/java/org/jabref/logic/preview/PreviewLayout.java[R49-52]

+        // Text-based (customized) styles are resolved by stable id, not display name — names are user-editable.
+        return customizedPreviewLayouts.stream()
+                                       .filter(c -> c.id().equals(layoutIdentifier))
+                                       .findFirst()

Evidence
PreviewLayout.of only matches customized layouts by id; existing migrations rewrite stored cycle
values to the "PREVIEW" identifier; and legacy migration currently creates a CustomizedPreviewStyle
via the (name,text) constructor which generates a random id, so "PREVIEW" cannot match any stored
customized-style id.
jablib/src/main/java/org/jabref/logic/preview/PreviewLayout.java[32-55]
jabgui/src/main/java/org/jabref/migrations/PreferencesMigrations.java[313-317]
jabgui/src/main/java/org/jabref/gui/preferences/JabRefGuiPreferences.java[999-1010]
jablib/src/main/java/org/jabref/logic/preview/CustomizedPreviewStyle.java[10-15]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Customized preview styles are now resolved by stable id (`PreviewLayout.of`), but legacy persisted cycle entries can contain `TextBasedPreviewLayout.NAME` ("PREVIEW"). The current migration stores legacy text as a new `CustomizedPreviewStyle(name,text)` which generates a random id, so the cycle entry "PREVIEW" no longer matches any customized-style id and gets filtered out.
### Issue Context
There is already an existing preferences migration that rewrites stored cycle entries to `TextBasedPreviewLayout.NAME` ("PREVIEW"), so this mismatch will occur on real upgrades.
### Fix Focus Areas
- jablib/src/main/java/org/jabref/logic/preview/PreviewLayout.java[32-55]
- jabgui/src/main/java/org/jabref/gui/preferences/JabRefGuiPreferences.java[908-930]
- jabgui/src/main/java/org/jabref/gui/preferences/JabRefGuiPreferences.java[999-1013]
### Suggested fix approach
Implement a backward-compatibility mapping so that legacy cycle identifier `TextBasedPreviewLayout.NAME` resolves to the migrated/default customized style id.
Options (pick one, but be consistent):
1) In `migrateLegacyCustomLayout`, preserve the legacy identifier as the **id** (e.g., `new CustomizedPreviewStyle(TextBasedPreviewLayout.NAME, <displayName>, legacyText)`), so existing cycles referencing "PREVIEW" still resolve.
2) In `JabRefGuiPreferences.getPreviewLayouts` (or `PreviewLayout.of`), special-case `layoutIdentifier.equals(TextBasedPreviewLayout.NAME)` to resolve to the first customized style (or the migrated legacy style).
3) Additionally (or alternatively), migrate stored `PREVIEW_CYCLE` entries from "PREVIEW" to the newly created customized-style id during migration.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. ~~Non-/// doc comments added~~ ✓ Resolved 📘 Rule violation ⚙ Maintainability

Description

New multi-line documentation-style comments use // instead of required Markdown Javadoc ///,
reducing consistency with the mandated documentation format. Convert these comment blocks to ///
Markdown Javadoc style.

Code

jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTabViewModel.java[R636-639]

+    // Commits an edit made in the style-name field to the currently selected TextBasedPreviewLayout.
+    // No-ops for non-customized (CSL/BST) selections. Reverts the field on blank/duplicate input.
+    // [impl->req~entry-preview.rename-custom-style~1]
+    public void renameSelectedStyle(@NonNull String newName) {

Evidence
PR Compliance ID 10 requires multi-line documentation comments to use ///. The PR introduces
multi-line, doc-style comment blocks using // above renameSelectedStyle and the
CustomizedPreviewStyle record.
AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments: AGENTS.md: Use Markdown Javadoc Comments (///) for Multi-line Documentation Comments
jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTabViewModel.java[636-668]
jablib/src/main/java/org/jabref/logic/preview/CustomizedPreviewStyle.java[6-9]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Multi-line documentation comments were introduced using `//` instead of the required Markdown Javadoc `///` format.
## Issue Context
The codebase standardizes multi-line documentation comments on `///` to keep generated docs and inline documentation consistent.
## Fix Focus Areas
- jabgui/src/main/java/org/jabref/gui/preferences/preview/PreviewTabViewModel.java[636-639]
- jablib/src/main/java/org/jabref/logic/preview/CustomizedPreviewStyle.java[6-9]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

4. ~~Requirement IDs improperly formatted~~ ✓ Resolved 📘 Rule violation ⚙ Maintainability

Description

The new OpenFastTrace requirements use ## headings and wrap req~...~1 identifiers in backticks,
deviating from the required ### + plain identifier-line format. This may break requirement
parsing/trace tooling.

Code

docs/requirements/entry-preview.md[R6-8]

+## Entry Preview shows the Available Panel split into CSL and Customized tabs
+`req~entry-preview.tabs~1`
+

Evidence
PR Compliance ID 34 specifies ### headings and an immediate plain req~...~1 identifier line. The
added requirements file uses ## headings and backticked identifiers.
AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Add OpenFastTrace Requirement Entries for New Features/Significant Fixes Using Correct Format: AGENTS.md: Requirements Tracing: Ad...

… fix comments, fix and add unit tests, migration tests added, update migration, fix rename bugs

…file

…yles

…of entry-preview.md file

…tps://github.com/bgyoo970/jabref into 16075-Support-multiple-customized-preview-styles

calixtus · 2026-08-21T08:16:35Z

Hi, just a very quick review of ui without looking into code:
The two new buttons are a bit misplaced, as there are already the buttons with chevrons for moving items from available to selected and back in the next column. too much information, ui looks ripped apart.

The "add new" button should go below the list it belongs to. Maybe also with a text-input for the new name of the new item. See custom entry types. This can maybe combined with "Add BST" as a menu button to add bst or custom or select from different templates.

The remove and edit buttons should go to the right inside of every line for the removable and editable items. Should only show up when hovering the mouse.

Indicator for customized is also too prominent. Think instead of a filename. Common indicator of a dirty flag is an asterisk.

koppor

Adress the UX issues identified at #16615 (comment)

bgyoo970 · 2026-08-28T18:37:58Z

Hi, sorry for the delay, I got caught up with a few other things. I'll address this as soon as I can

…the customized list along with a menu button to add different styles. Remove and edit buttons added as a part of listCell onHover. dedicated rename text field removed in favor of hovering edit buttons. dedicated text box added to add new custom style

…yles

bgyoo970 · 2026-09-02T01:02:31Z

Hi, just a very quick review of ui without looking into code: The two new buttons are a bit misplaced, as there are already the buttons with chevrons for moving items from available to selected and back in the next column. too much information, ui looks ripped apart.

The "add new" button should go below the list it belongs to. Maybe also with a text-input for the new name of the new item. See custom entry types. This can maybe combined with "Add BST" as a menu button to add bst or custom or select from different templates.

The remove and edit buttons should go to the right inside of every line for the removable and editable items. Should only show up when hovering the mouse.

Indicator for customized is also too prominent. Think instead of a filename. Common indicator of a dirty flag is an asterisk.

I added the changes to move the add custom style and 'Add BST' functionality down below the customized list. Likewise, I added functionality to edit and delete a list cell when hovering the mouse.

However, I'm not too sure what you meant about the indicator for customized. I shouldn't have a particular indicator or symbol that distinguishes a custom style in the list cell itself. However, the customized styles that get created do spawn under the customized tab list view.

bgyoo970 and others added 25 commits August 11, 2026 00:23

[JabRef#16075] Add record to help persist customized styles

405dfb1

Merge branch 'JabRef:main' into controltest

b07691a

Merge branch 'main' of https://github.com/bgyoo970/jabref

908cf4e

Merge pull request #1 from bgyoo970/controltest

bb94a2d

Merge changes into forked main branch

Merge branch 'main' of https://github.com/bgyoo970/jabref

902d2cc

[JabRef#16075] Added unit tests for previewTabViewModel, added string…

9d11263

… constants to jabref_en.properties, refactored naming for CustomizedPreviewStyle

Revert "[JabRef#16075] Added unit tests for previewTabViewModel, adde…

d69939b

…d string constants to jabref_en.properties, refactored naming for CustomizedPreviewStyle" This reverts commit 9d11263.

[JabRef#16075] rolledback last commit and recommit same changes from …

b77e4a6

…last commit, minus changes to abbrv.jabref.org and csl-styles

[JabRef#16075] Clean up comments, add remaining unit tests, fix nomen…

2e97f9d

…clature

[JabRef#16075] fixed comment

f3356d6

resolve merge conflicts

d3b1248

Merge branch 'JabRef-main'

7f06562

Merge branch 'JabRef:main' into main

664f368

[JabRef#16075] address checklist.md items and fix issues. cleaned up …

e663d51

…comments and null checks. used modern Java for factory instead of constructor. updated string in JabRef_en.properties. updated changelog and created entry-preivew.md with new features.

Fix submodules, fix unit test

b546643

Merge branch 'JabRef:main' into 16075-Support-multiple-customized-pre…

84514b9

…view-styles

Fix submodules

088b870

Fix submodules

ed5546d

Merge remote-tracking branch 'upstream/main' into 16075-Support-multi…

ba42db8

…ple-customized-preview-styles

fix submodule for csl-styles

10316b4

fix submodule for abbrv.jabref.org

c61ef66

[JabRef#16075] Clean up comments, merge latest changes

fbf1784

Merge branch 'JabRef:main' into 16075-Support-multiple-customized-pre…

8b09165

…view-styles

github-actions Bot added good first issue An issue intended for project-newcomers. Varies in difficulty. component: entry-preview labels Aug 17, 2026

Merge branch 'JabRef:main' into 16075-Support-multiple-customized-pre…

5f341fa

…view-styles

github-actions Bot added the status: changes-required Pull requests that are not yet complete label Aug 17, 2026

qodo-free-for-open-source-projects Bot reviewed Aug 17, 2026

View reviewed changes

github-actions Bot mentioned this pull request Aug 17, 2026

Support multiple customized preview styles #16075

Open

bgyoo970 and others added 6 commits August 18, 2026 22:17

[JabRef#16075] resolving violations, update description in .md files,…

d440f50

… fix comments, fix and add unit tests, migration tests added, update migration, fix rename bugs

[JabRef#16075] add unit test files for migration tests and util test …

ae6d946

…file

Merge branch 'main' into 16075-Support-multiple-customized-preview-st…

b1c0320

…yles

[JabRef#16075] updating util file for toolkit error, updating format …

644cd93

…of entry-preview.md file

Merge branch '16075-Support-multiple-customized-preview-styles' of ht…

0295433

…tps://github.com/bgyoo970/jabref into 16075-Support-multiple-customized-preview-styles

[JabRef#16075] Resolve checkstyle issue, removing unused import

59db63f

github-actions Bot added status: no-bot-comments and removed status: changes-required Pull requests that are not yet complete labels Aug 19, 2026

bgyoo970 mentioned this pull request Aug 19, 2026

[Issue-16075] Support multiple customized preview styles #16589

Closed

42 tasks

github-actions Bot added status: changes-required Pull requests that are not yet complete and removed status: no-bot-comments labels Aug 24, 2026

koppor requested changes Aug 28, 2026

View reviewed changes

koppor mentioned this pull request Aug 28, 2026

Remove stale conflict comment once PR is mergeable again #16721

Merged

8 tasks

github-actions Bot added the component: preferences label Sep 1, 2026

bgyoo970 and others added 2 commits September 1, 2026 14:02

Merge branch 'main' into 16075-Support-multiple-customized-preview-st…

a562c98

…yles

[JabRef#16075] update tests and jabRef_en constants

fceaa00

github-actions Bot added status: no-bot-comments and removed status: changes-required Pull requests that are not yet complete labels Sep 1, 2026

Navigation Menu

Uh oh!

Uh oh!

16075 support multiple customized preview styles - #16615

16075 support multiple customized preview styles#16615
bgyoo970 wants to merge 35 commits into
JabRef:mainfrom
bgyoo970:16075-Support-multiple-customized-preview-styles

bgyoo970 commented Aug 17, 2026 •

edited

Loading

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 17, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 17, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

calixtus commented Aug 21, 2026 •

edited

Loading

Uh oh!

koppor left a comment

Uh oh!

bgyoo970 commented Aug 28, 2026

Uh oh!

bgyoo970 commented Sep 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Uh oh!

Conversation

bgyoo970 commented Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Analogies

Steps to test

Related issues and pull requests

AI usage

Nullability and control flow

Exceptions

Style and idioms

User-facing text

Security

Tests

2. Verification commands

3. Documentation

4. Pull request

Checklist

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 17, 2026

PR Summary by Qodo

Uh oh!

qodo-free-for-open-source-projects Bot commented Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

calixtus commented Aug 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

koppor left a comment

Choose a reason for hiding this comment

Uh oh!

bgyoo970 commented Aug 28, 2026

Uh oh!

bgyoo970 commented Sep 2, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

bgyoo970 commented Aug 17, 2026 •

edited

Loading

qodo-free-for-open-source-projects Bot commented Aug 17, 2026 •

edited

Loading

calixtus commented Aug 21, 2026 •

edited

Loading