Skip to content

Update IntelliJ settings#15629

Merged
Siedlerchr merged 1 commit into
mainfrom
refine-code-style
Apr 28, 2026
Merged

Update IntelliJ settings#15629
Siedlerchr merged 1 commit into
mainfrom
refine-code-style

Conversation

@koppor

@koppor koppor commented Apr 27, 2026

Copy link
Copy Markdown
Member

Ports code style from the larger PR.

Steps to test

Fire up IntelliJ

Checklist

  • 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 added a screenshot in the PR description showing a library with a single entry with me as author and as title the issue number
  • [/] I described the change in CHANGELOG.md in a way that can be understood by the average user (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

Co-authored-by: Ruslan <ruslanpopov1512@gmail.com>
@qodo-free-for-open-source-projects

Copy link
Copy Markdown
Contributor

Review Summary by Qodo

Refine IntelliJ and editor configuration settings

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Add Properties code style settings for blank line preservation
• Expand project dictionary with new technical terms
• Update VS Code spell checker dictionary with AI and tool-related words
Diagram
flowchart LR
  A["Code Style Config"] -->|Add Properties settings| B["IntelliJ Project.xml"]
  C["Project Dictionary"] -->|Add technical terms| D["Dictionary Updates"]
  E["VS Code Config"] -->|Add spell check words| F["LTeX Dictionary"]
Loading

Grey Divider

File Changes

1. .idea/codeStyles/Project.xml ⚙️ Configuration changes +3/-0

Add Properties code style configuration

• Added Properties language code style settings
• Configured KEEP_BLANK_LINES option to true for Properties files
• Preserves blank lines in Properties file formatting

.idea/codeStyles/Project.xml


2. .idea/dictionaries/project.xml ⚙️ Configuration changes +1/-0

Add summarizator to project dictionary

• Added new word "summarizator" to project dictionary
• Expands IntelliJ spell checker vocabulary

.idea/dictionaries/project.xml


3. .vscode/ltex.dictionary.en-US.txt ⚙️ Configuration changes +8/-0

Expand VS Code spell checker dictionary

• Added 8 new words to VS Code spell checker dictionary
• Includes AI/ML terms (HuggingFace, vLLM, Ollama)
• Includes technical abbreviations (impl, utest, dsn, de-facto)

.vscode/ltex.dictionary.en-US.txt


Grey Divider

Qodo Logo

@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Apr 27, 2026

Copy link
Copy Markdown
Contributor

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

Grey Divider


Remediation recommended

1. Missing final newline 🐞 Bug ⚙ Maintainability
Description
.idea/dictionaries/project.xml is committed without a trailing newline, violating the repository’s
EditorConfig (insert_final_newline = true). This can cause persistent formatting churn
(editors/formatters re-writing the file) and noisy diffs across environments.
Code

.idea/dictionaries/project.xml[R8-11]

+      <w>summarizator</w>
    </words>
  </dictionary>
</component>
Evidence
The repository declares a global requirement to always insert a final newline, but the PR diff for
.idea/dictionaries/project.xml indicates it has no newline at end-of-file (`\ No newline at end of
file`). This contradicts the EditorConfig rule and will commonly lead to tooling reformatting the
file or repeated diffs.

.editorconfig[1-7]
.idea/dictionaries/project.xml[1-11]

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

### Issue description
`.idea/dictionaries/project.xml` is missing a trailing newline at end-of-file, which violates `.editorconfig` (`insert_final_newline = true`).

### Issue Context
This is a formatting consistency requirement and helps prevent future diffs when editors/formatters normalize the file.

### Fix Focus Areas
- .idea/dictionaries/project.xml[1-11]
- .editorconfig[1-7]

### Suggested change
Ensure the file ends with a single `\n` after the closing `</component>`.

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


Grey Divider

Qodo Logo

@koppor koppor added the status: ready-for-review Pull Requests that are ready to be reviewed by the maintainers label Apr 27, 2026
@Siedlerchr Siedlerchr merged commit 3121859 into main Apr 28, 2026
78 checks passed
@Siedlerchr Siedlerchr deleted the refine-code-style branch April 28, 2026 14:23
Siedlerchr added a commit that referenced this pull request May 1, 2026
…urityIssues

* upstream/fixSecurityIssues:
  fix jbang (#15649)
  Add initial claude action support
  Chore(deps): Bump org.glassfish.grizzly:grizzly-bom in /versions (#15648)
  Update IntelliJ settings (#15629)
  Chore(deps): Bump org.openrewrite.recipe:rewrite-recipe-bom (#15626)
  Fixed year not appearing on citation key for In-* entries due to orphaned crossref links (#9071) (#15582)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: ready-for-review Pull Requests that are ready to be reviewed by the maintainers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants