Fix: Optimize UI layout for Web Search preferences #14819

TimeTriggerx · 2026-01-07T03:24:33Z

User description

The "Search Engine URL Templates" table in Preferences > Web Search was consuming excessive vertical space due to a VBox.vgrow="ALWAYS" constraint on the TableView, creating a large empty gap in the UI.

Changes:

Replaced the heavy TableView control with a lightweight VBox container.
Removed the "Press return to commit" label as it is no longer needed for standard text fields.

Screenshots

Before:

After (Fix):

Mandatory checks

I own the copyright of the code submitted and I license it under the MIT license
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 described the change in CHANGELOG.md in a way that is understandable for the average user (minor change).
[/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

PR Type

Bug fix, Enhancement

Description

Replace TableView with dynamic VBox layout for search engines
Remove excessive vertical space in Web Search preferences UI
Simplify search engine display with label and text field
Remove obsolete localization keys and "Press return" hint

Diagram Walkthrough

flowchart LR
  A["TableView with vgrow ALWAYS"] -- "Replace with" --> B["Dynamic VBox layout"]
  B -- "Render each engine as" --> C["HBox with Label and TextField"]
  D["Remove TableColumn setup"] -- "Simplify to" --> E["Direct property binding"]
  F["Obsolete localization keys"] -- "Delete" --> G["Clean properties file"]

File Walkthrough

Relevant files

Enhancement

WebSearchTab.java `Replace TableView with dynamic VBox rendering` jabgui/src/main/java/org/jabref/gui/preferences/websearch/WebSearchTab.java Removed TableView and TableColumn imports and FXML bindings Replaced table initialization with dynamic VBox-based rendering Added `createSearchEngineNode()` method to build HBox containers with Label and TextField Implemented InvalidationListener to update search engine list on changes Simplified search engine display from editable table cells to bound text fields	+30/-15
WebSearchTab.fxml `Simplify FXML layout from table to VBox` jabgui/src/main/resources/org/jabref/gui/preferences/websearch/WebSearchTab.fxml Removed TableView and TableColumn XML imports Replaced entire TableView element with simple VBox container Removed "Press return to commit" instructional label Removed table column definitions and resize policy configuration Added `searchEngineContainer` VBox with 10px spacing	+1/-22

Documentation

JabRef_en.properties `Remove obsolete table column localization keys` jablib/src/main/resources/l10n/JabRef_en.properties Removed localization key "Search Engine" Removed localization key "URL Template" Kept "Search Engine URL Templates" section header	+0/-2

Replaced the large TableView with a dynamic VBox layout to remove unused vertical space.

qodo-free-for-open-source-projects · 2026-01-07T03:25:04Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Missing Input Validation: The `urlField` TextField at line 187 binds directly to `item.urlTemplateProperty()` without visible validation or sanitization of URL input. Referred Code urlField.textProperty().bindBidirectional(item.urlTemplateProperty()); HBox.setHgrow(urlField, Priority.ALWAYS); // Grow to fill space Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

qodo-free-for-open-source-projects · 2026-01-07T03:26:31Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Prevent memory leak with weak listener To prevent a potential memory leak, wrap the `searchEngineListener` in a `WeakInvalidationListener` before adding it to `viewModel.getSearchEngines()`. This allows the `WebSearchTab` to be garbage collected properly. jabgui/src/main/java/org/jabref/gui/preferences/websearch/WebSearchTab.java [81-91] // Bind search engine list to the UI container InvalidationListener searchEngineListener = _ -> searchEngineContainer .getChildren() .setAll(viewModel.getSearchEngines() .stream() .map(this::createSearchEngineNode) .toList()); // Initialize the list and add listener for future updates searchEngineListener.invalidated(null); -viewModel.getSearchEngines().addListener(searchEngineListener); +viewModel.getSearchEngines().addListener(new javafx.beans.WeakInvalidationListener(searchEngineListener)); Apply / Chat Suggestion importance[1-10]: 9 __ Why: This suggestion correctly identifies a potential memory leak caused by a long-lived view model holding a strong reference to a listener in a shorter-lived UI component. Using a `WeakInvalidationListener` is the standard and correct way to prevent this in JavaFX, making this a critical fix for application stability.	High
Learned best practice	Extract lambda to method reference Replace the lambda expression with a method reference for better readability and conciseness. Extract the logic into a separate method and use a method reference. jabgui/src/main/java/org/jabref/gui/preferences/websearch/WebSearchTab.java [82-87] -InvalidationListener searchEngineListener = _ -> searchEngineContainer +InvalidationListener searchEngineListener = _ -> updateSearchEngineContainer(); + +private void updateSearchEngineContainer() { + searchEngineContainer .getChildren() .setAll(viewModel.getSearchEngines() .stream() .map(this::createSearchEngineNode) .toList()); +} `[To ensure code accuracy, apply this suggestion manually]` Suggestion importance[1-10]: 6 __ Why: Relevant best practice - Use method references instead of lambda expressions when the lambda only calls a single method with the same parameters	Low
Update

koppor · 2026-01-07T15:35:03Z

No screenshot before
Headings are lost (which is IMHO OK, BUT ADAPT THE LOCALIZATON AS THE TEST SAYS - **why is there no reaction on the the failing test since 12 hours?)

TimeTriggerx · 2026-01-07T17:31:36Z

Apologies for the delay @koppor ! I missed the notification earlier. Now fault is mended and order restored.

qodo-free-for-open-source-projects · 2026-01-07T17:32:45Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

qodo-free-for-open-source-projects · 2026-01-07T17:33:41Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Refactor UI update logic for clarity Refactor the UI update logic by extracting it from the `InvalidationListener` into a separate, clearly-named method. This improves readability by avoiding the unconventional `listener.invalidated(null)` call for initialization. jabgui/src/main/java/org/jabref/gui/preferences/websearch/WebSearchTab.java [81-91] -// Bind search engine list to the UI container -InvalidationListener searchEngineListener = _ -> searchEngineContainer - .getChildren() - .setAll(viewModel.getSearchEngines() - .stream() - .map(this::createSearchEngineNode) - .toList()); +// Create and bind the search engine list to the UI +viewModel.getSearchEngines().addListener((InvalidationListener) _ -> updateSearchEngineList()); +updateSearchEngineList(); -// Initialize the list and add listener for future updates -searchEngineListener.invalidated(null); -viewModel.getSearchEngines().addListener(searchEngineListener); - Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies that calling `invalidated(null)` is an unconventional use of a listener. Extracting the logic into a named method improves code clarity and maintainability, making the developer's intent more explicit.	Low
More

calixtus · 2026-01-08T14:05:51Z

A vertical gap usually 10 should be visible between controls

…h-ui

…gerx/jabref into fix-14556-web-search-ui

qodo-free-for-open-source-projects · 2026-01-08T17:24:49Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Missing URL validation: The TextField for URL template is bound bidirectionally without visible input validation or sanitization in the displayed code Referred Code TextField urlField = new TextField(); urlField.textProperty().bindBidirectional(item.urlTemplateProperty()); HBox.setHgrow(urlField, Priority.ALWAYS); // Grow to fill space Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

qodo-free-for-open-source-projects · 2026-01-08T17:26:11Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Refactor UI update logic for clarity Refactor the UI update logic to use a `Runnable` for better clarity. This involves defining the update logic in a `Runnable`, calling it directly for the initial setup, and then using it within the listener for subsequent updates. jabgui/src/main/java/org/jabref/gui/preferences/websearch/WebSearchTab.java [81-91] -// Bind search engine list to the UI container -InvalidationListener searchEngineListener = _ -> searchEngineContainer +// Define the update logic +Runnable updateSearchEnginesView = () -> searchEngineContainer .getChildren() .setAll(viewModel.getSearchEngines() .stream() .map(this::createSearchEngineNode) .toList()); -// Initialize the list and add listener for future updates -searchEngineListener.invalidated(null); -viewModel.getSearchEngines().addListener(searchEngineListener); +// Initial population +updateSearchEnginesView.run(); +// Add listener for future updates +viewModel.getSearchEngines().addListener(obs -> updateSearchEnginesView.run()); + Apply / Chat Suggestion importance[1-10]: 5 __ Why: The suggestion correctly identifies an unconventional use of `invalidated(null)` to trigger an action and proposes a clearer, more standard pattern using a `Runnable`, which improves code readability and maintainability.	Low
More

qodo-free-for-open-source-projects · 2026-01-17T11:15:35Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Missing null check: The `createSearchEngineNode()` method does not validate if `item` parameter is null before accessing its properties. Referred Code private Node createSearchEngineNode(SearchEngineItem item) { HBox container = new HBox(10); container.setAlignment(Pos.CENTER_LEFT); // 1. Label for the Name (e.g., "Google Scholar") Label nameLabel = new Label(); nameLabel.textProperty().bind(item.nameProperty()); nameLabel.setMinWidth(120); // Keep alignment consistent nameLabel.setPrefWidth(120); // 2. TextField for the URL TextField urlField = new TextField(); urlField.textProperty().bindBidirectional(item.urlTemplateProperty()); HBox.setHgrow(urlField, Priority.ALWAYS); // Grow to fill space container.getChildren().addAll(nameLabel, urlField); return container; } Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: No URL validation: The `urlField` bound to `item.urlTemplateProperty()` lacks input validation to ensure URLs are properly formatted and safe. Referred Code TextField urlField = new TextField(); urlField.textProperty().bindBidirectional(item.urlTemplateProperty()); HBox.setHgrow(urlField, Priority.ALWAYS); // Grow to fill space Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

qodo-free-for-open-source-projects · 2026-01-17T11:16:47Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category Suggestion Impact

Possible issue

Unbind properties to prevent memory leaks

To prevent a memory leak, unbind the nameLabel and urlField properties when
their parent node is removed from the scene by adding a listener to the
container's sceneProperty.

jabgui/src/main/java/org/jabref/gui/preferences/websearch/WebSearchTab.java [175-192]

 private Node createSearchEngineNode(SearchEngineItem item) {
     HBox container = new HBox(10);
     container.setAlignment(Pos.CENTER_LEFT);
 
     // 1. Label for the Name (e.g., "Google Scholar")
     Label nameLabel = new Label();
     nameLabel.textProperty().bind(item.nameProperty());
     nameLabel.setMinWidth(120); // Keep alignment consistent
     nameLabel.setPrefWidth(120);
 
     // 2. TextField for the URL
     TextField urlField = new TextField();
     urlField.textProperty().bindBidirectional(item.urlTemplateProperty());
     HBox.setHgrow(urlField, Priority.ALWAYS); // Grow to fill space
 
     container.getChildren().addAll(nameLabel, urlField);
+
+    // Unbind properties when the node is removed from the scene to prevent memory leaks
+    container.sceneProperty().addListener((obs, oldScene, newScene) -> {
+        if (newScene == null) {
+            nameLabel.textProperty().unbind();
+            urlField.textProperty().unbindBidirectional(item.urlTemplateProperty());
+        }
+    });
+
     return container;
 }

Apply / Chat

Suggestion importance[1-10]: 9

__

Why: The suggestion correctly identifies a memory leak introduced by the new dynamic UI creation, where old UI nodes are not garbage collected because their property bindings are not removed. This is a critical issue that affects application stability.

High

More

FIX JabRef#14556

6cddda1

Replaced the large TableView with a dynamic VBox layout to remove unused vertical space.

TimeTriggerx changed the title ~~FIX #14556~~ Fix: Optimize UI layout for Web Search preferences #14556 Jan 7, 2026

github-actions bot added the good first issue An issue intended for project-newcomers. Varies in difficulty. label Jan 7, 2026

qodo-free-for-open-source-projects bot added the Review effort 2/5 label Jan 7, 2026

github-actions bot added the status: changes-required Pull requests that are not yet complete label Jan 7, 2026

TimeTriggerx changed the title ~~Fix: Optimize UI layout for Web Search preferences #14556~~ Fix: Optimize UI layout for Web Search preferences Jan 7, 2026

TimeTriggerx marked this pull request as draft January 7, 2026 15:49

Remove obsolete localization keys 'Search Engine' and 'URL Template'

3182aef

github-actions bot removed the status: changes-required Pull requests that are not yet complete label Jan 7, 2026

TimeTriggerx marked this pull request as ready for review January 7, 2026 17:32

Merge branch 'main' into fix-14556-web-search-ui

28bb966

TimeTriggerx marked this pull request as draft January 8, 2026 01:43

TimeTriggerx marked this pull request as ready for review January 8, 2026 02:28

TimeTriggerx added 4 commits January 8, 2026 22:26

Merge remote-tracking branch 'upstream/main' into fix-14556-web-searc…

a5295e0

…h-ui

Add 10px vertical gap

e0862aa

Merge branch 'main' into fix-14556-web-search-ui

3fa5667

Merge branch 'fix-14556-web-search-ui' of https://github.com/TimeTrig…

49bef8f

…gerx/jabref into fix-14556-web-search-ui

TimeTriggerx marked this pull request as draft January 8, 2026 17:14

TimeTriggerx marked this pull request as ready for review January 8, 2026 17:24

Merge branch 'main' into fix-14556-web-search-ui

8f4b414

TimeTriggerx marked this pull request as draft January 17, 2026 11:14

Merge branch 'main' into fix-14556-web-search-ui

196051e

TimeTriggerx marked this pull request as ready for review January 17, 2026 11:15

koppor added the status: ready-for-review Pull Requests that are ready to be reviewed by the maintainers label Jan 18, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Fix: Optimize UI layout for Web Search preferences #14819

Fix: Optimize UI layout for Web Search preferences #14819

TimeTriggerx commented Jan 7, 2026 •

edited by qodo-free-for-open-source-projects bot

Loading

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 7, 2026 •

edited

Loading

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 7, 2026 •

edited

Loading

Uh oh!

koppor commented Jan 7, 2026 •

edited

Loading

Uh oh!

TimeTriggerx commented Jan 7, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 7, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 7, 2026

Uh oh!

calixtus commented Jan 8, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 8, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 8, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 17, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Fix: Optimize UI layout for Web Search preferences #14819

Are you sure you want to change the base?

Fix: Optimize UI layout for Web Search preferences #14819

Conversation

TimeTriggerx commented Jan 7, 2026 • edited by qodo-free-for-open-source-projects bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

User description

Screenshots

Mandatory checks

PR Type

Description

Diagram Walkthrough

File Walkthrough

Uh oh!

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

Uh oh!

PR Compliance Guide 🔍

Uh oh!

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

Uh oh!

PR Code Suggestions ✨

Uh oh!

koppor commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

TimeTriggerx commented Jan 7, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 7, 2026

PR Compliance Guide 🔍

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 7, 2026

PR Code Suggestions ✨

Uh oh!

calixtus commented Jan 8, 2026

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 8, 2026

PR Compliance Guide 🔍

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 8, 2026

PR Code Suggestions ✨

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 17, 2026

PR Compliance Guide 🔍

Uh oh!

qodo-free-for-open-source-projects bot commented Jan 17, 2026

PR Code Suggestions ✨

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

TimeTriggerx commented Jan 7, 2026 •

edited by qodo-free-for-open-source-projects bot

Loading

qodo-free-for-open-source-projects bot commented Jan 7, 2026 •

edited

Loading

qodo-free-for-open-source-projects bot commented Jan 7, 2026 •

edited

Loading

koppor commented Jan 7, 2026 •

edited

Loading