InlineProblems

Plugin to show problems like errors and warnings inside the text editor (inline) for IDEs based on the IntelliJ Platform, inspired by Error Lens and InlineError.

You can turn this plugin on and off with the keyboard shortcut alt+u, additional shortcuts can be configured in the settings.

Jetbrains Marketplace . Codeberg · Github . Report Bug · Request Feature

---

Screenshots

Table of Contents

1. About The Project
2. Getting Started
3. Beta Versions
4. Roadmap
5. License
6. Contact

About The Project

• I use this plugin professionally on a daily basis in IntelliJ and CLion in combination with the IdeaVIM extension

Getting Started

• Clone the repository and open it with IntelliJ
• The plugin targets the IntelliJ Platform 2025.1.7 and Java 21 (see gradle.properties), and builds with Gradle 9, so any JDK from 17 up to the current one works: ./gradlew buildPlugin
• Useful tasks:
  • buildPlugin - builds the distribution ZIP
  • runIde - starts a sandbox IDE with the plugin
  • verifyPluginStructure - descriptor and archive structure check
  • verifyPlugin - IntelliJ Plugin Verifier, binary compatibility against the IDE pinned in pluginVerifierIdeVersions
  • printProductsReleases - lists the IDE builds available for the verifier
• Lombok is used, so the Lombok plugin has to be enabled in the development IDE

Releasing

Branches: features are merged into main, release holds what is published. Both are protected, so everything goes through pull requests.

1. Changelog - every change is listed in the [Unreleased] section of CHANGELOG.md, in the pull request that makes it
2. Prepare - run the "Prepare Release" workflow from the Actions tab with the new version, e.g. 0.6.2. It raises pluginVersion in gradle.properties, moves the [Unreleased] section under ## [0.6.2] and opens the pull request "Prepare the 0.6.2 release" to main. The workflow stops if [Unreleased] is empty. No checks run on this pull request, it is created with the GITHUB_TOKEN
3. Merge into main
4. Beta - open the pull request main -> release, titled "main -> release for 0.6.2" with the changelog entry as description. The Beta Release workflow publishes 0.6.2-beta+RC<run>.<attempt> to the Marketplace beta channel and creates the GitHub prerelease v0.6.2-beta with the changelog. Every new commit on the pull request publishes a new beta
5. Merge into release - once the beta is fine. The Build workflow on release creates the release draft v0.6.2 with the notes of the [0.6.2] section, targeting the merged commit
6. Release - publish the release draft v0.6.2 on GitHub. The Release workflow publishes the plugin to the Marketplace default and beta channels and attaches the ZIP to the release

The "What's new" on the Marketplace comes from the changelog section of the version, for a beta too. Changes merged after step 2 belong under the version section, not under [Unreleased].

Beta Versions

Download

• You can download beta versions from the GitHub release page, there are available as pre-releases.

Custom Repository

• Add https://plugins.jetbrains.com/plugins/beta/20789 as custom plugin repository if you only want this plugin from the beta channel
• Add https://plugins.jetbrains.com/plugins/beta/list as custom plugin repository and you get all plugins with builds in the beta channel

Roadmap

• Multiline ErrorLabels (Inlays)
• Delay before adding problems (#60, #78)
• Listen to changed width of editor and redraw labels if needed (#57)

See the open issues for the full list.

License

Distributed under the GNU General Public License v3 See LICENSE for more information.

Contact

Julian Hackinger - dev@hackinger.net

Project Link: https://github.com/0verEngineer/InlineProblems