• Add bracket wrapping shorthand for protecting terms in fields
• When user selects text and types '{', selection wraps in brackets
• Implement via KeyEvent filter in FieldEditorFX component
• Include comprehensive unit tests and changelog documentation

Implement bracket wrapping for selected text

• Add KeyEvent filter to intercept '{' character input
• Check if text is selected when '{' is typed
• Wrap selected text with opening and closing braces
• Consume event to prevent default character insertion

jabgui/src/main/java/org/jabref/gui/fieldeditors/FieldEditorFX.java

Add unit tests for bracket wrapping feature

• Create new test class extending ApplicationTest for GUI testing
• Test wrapping behavior when '{' typed with active selection
• Test normal insertion when '{' typed without selection
• Use TestFX framework for interactive field testing

jabgui/src/test/java/org/jabref/gui/fieldeditors/FieldEditorFXTest.java

Document bracket wrapping feature in changelog

• Add entry documenting the new bracket wrapping shorthand feature
• Describe functionality as quick way to protect terms in fields
• Reference PR #15442 for tracking

CHANGELOG.md

Description

FieldEditorFX.establishBinding wraps the entire selected text including leading/trailing spaces when
'{' is typed, which differs from the existing “Protect selection” action that keeps surrounding
spaces outside the braces. This causes unexpected field-content changes for common selections like "
world " and contradicts the in-code claim of equivalence.

Code

jabgui/src/main/java/org/jabref/gui/fieldeditors/FieldEditorFX.java[R49-57]

+        // When '{' is typed with an active selection, wrap the selected text in '{…}' instead of replacing it.
+        // This is equivalent to the "Protect terms" option in the context menu.
+        textInputControl.addEventFilter(KeyEvent.KEY_TYPED, e -> {
+            if ("{".equals(e.getCharacter()) && textInputControl.getSelection().getLength() > 0) {
+                String selectedText = textInputControl.getSelectedText();
+                textInputControl.replaceSelection("{" + selectedText + "}");
+                e.consume();
+            }
+        });

Evidence

The new key-typed handler always does "{" + selectedText + "}", so any leading/trailing whitespace
becomes protected inside braces. The existing UI command “Protect selection” has explicit logic to
move leading/trailing spaces outside braces and to strip the wrapped term, showing that whitespace
handling is intended/important and that the new handler is not equivalent.

jabgui/src/main/java/org/jabref/gui/fieldeditors/FieldEditorFX.java[49-57]
jabgui/src/main/java/org/jabref/gui/fieldeditors/contextmenu/ProtectedTermsMenu.java[60-79]

Agent prompt

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

## Issue description
Typing `{` with an active selection currently wraps the *entire* selection, including leading/trailing spaces. This differs from the existing **Protect selection** behavior, which keeps surrounding spaces outside the braces and wraps the stripped term.
### Issue Context
`FieldEditorFX.establishBinding` claims the behavior is equivalent to the context menu “Protect terms”, but `ProtectedTermsMenu.ProtectSelectionAction` has special whitespace handling.
### Fix Focus Areas
- jabgui/src/main/java/org/jabref/gui/fieldeditors/FieldEditorFX.java[49-57]
- jabgui/src/main/java/org/jabref/gui/fieldeditors/contextmenu/ProtectedTermsMenu.java[60-79]
### Implementation notes
Replicate the `ProtectSelectionAction` logic in the key handler:
- compute `firstStr`/`lastStr` based on `selectedText.startsWith(" ")` and `selectedText.endsWith(" ")`
- wrap `selectedText.strip()`
- (optionally) adjust the comment to state the precise equivalence

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

Description

The newly added comments primarily describe what the code does rather than explaining
rationale/intent, making them trivial and adding noise. This violates the requirement that comments
should explain 'why' instead of restating obvious behavior.

Code

jabgui/src/main/java/org/jabref/gui/fieldeditors/FieldEditorFX.java[R49-50]

+        // When '{' is typed with an active selection, wrap the selected text in '{…}' instead of replacing it.
+        // This is equivalent to the "Protect terms" option in the context menu.

Evidence

PR Compliance ID 17 forbids trivial comments that merely describe code behavior; the added `// When
'{' is typed...` comment restates the immediately following event-filter logic instead of providing
rationale.

AGENTS.md
jabgui/src/main/java/org/jabref/gui/fieldeditors/FieldEditorFX.java[49-55]

Agent prompt

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

## Issue description
New comments describe what the code does (wrapping selection on `{` key typed) instead of explaining the rationale/intent, which is discouraged by the project's comment guidelines.
## Issue Context
The behavior is already clear from the event filter code; comments should focus on why this interception is needed (e.g., UX parity with "Protect terms", preventing replacement of selection), not restate the obvious.
## Fix Focus Areas
- jabgui/src/main/java/org/jabref/gui/fieldeditors/FieldEditorFX.java[49-55]

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

Description

FieldEditorFXTest only tests wrapping a selection without surrounding spaces, despite whitespace
being a documented special case in the existing “Protect selection” implementation. This leaves the
most likely behavior mismatch untested and allows regressions after fixing the whitespace behavior.

Code

jabgui/src/test/java/org/jabref/gui/fieldeditors/FieldEditorFXTest.java[R50-74]

+    @Test
+    void openingBraceWrapsSelectedText() {
+        interact(() -> {
+            textField.setText("hello world");
+            textField.selectRange(6, 11);
+            textField.fireEvent(new KeyEvent(
+                    textField, textField, KeyEvent.KEY_TYPED, "{", "{", KeyCode.UNDEFINED,
+                    false, false, false, false));
+        });
+
+        assertEquals("hello {world}", textField.getText());
+    }
+
+    @Test
+    void openingBraceWithoutSelectionInsertsNormally() {
+        interact(() -> {
+            textField.setText("hello");
+            textField.positionCaret(5);
+            textField.fireEvent(new KeyEvent(
+                    textField, textField, KeyEvent.KEY_TYPED, "{", "{", KeyCode.UNDEFINED,
+                    false, false, false, false));
+        });
+
+        assertEquals("hello{", textField.getText());
+    }

Evidence

The test covers only selecting "world" and typing '{'. The existing ProtectSelectionAction
explicitly handles leading/trailing spaces, implying this edge case should be verified for the new
shortcut too.

jabgui/src/test/java/org/jabref/gui/fieldeditors/FieldEditorFXTest.java[50-74]
jabgui/src/main/java/org/jabref/gui/fieldeditors/contextmenu/ProtectedTermsMenu.java[67-78]

Agent prompt

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

## Issue description
The new tests don’t cover selections with leading and/or trailing spaces, which is a known special case for brace-protection behavior.
### Issue Context
`ProtectedTermsMenu.ProtectSelectionAction` adjusts braces/spacing when selection starts/ends with spaces.
### Fix Focus Areas
- jabgui/src/test/java/org/jabref/gui/fieldeditors/FieldEditorFXTest.java[50-74]
### Test cases to add
Add 2–3 tests such as:
- selection includes leading space: "hello world" select " world" -> expect "hello {world}" or "hello {world}" with space preserved outside depending on intended behavior
- selection includes trailing space: "hello world" select "world " -> expect "hello {world} "
- selection includes both: select " world " -> expect "hello {world} "
(Align expected strings with the corrected implementation that matches ProtectSelectionAction.)

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