Feature: JetBrains IDE plugin (Rider/IntelliJ) for OKF bundles

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java, kotlin

Research direction

Start by reading CONTRIBUTING.md and discuss the cross-language integration approach and whether the plugin belongs in this repository or a companion repository. The proposal points to a new JetBrains plugin project using the IntelliJ Gradle toolchain and the okf CLI; no file paths or tests are specified. Done means it builds, loads in a Rider or IntelliJ sandbox, and reports the same diagnostics as okf validate on the same bundle.

Written by the indexing model from the issue text.

Description

enhancement help wanted

Difficulty / est. effort: large, exploratory (new project + non-.NET toolchain)

Context: A native JetBrains IDE plugin (Rider / IntelliJ) would let JetBrains users browse, validate, and navigate an OKF bundle directly in the IDE. This is a larger, exploratory feature — please discuss the design in a Discussion or on this issue first, especially the cross-language integration approach.

Scope (proposal — refine in discussion):

  • A JetBrains plugin (Kotlin/Java, Gradle IntelliJ Plugin toolchain) — this lives outside the .NET solution, likely in its own directory (e.g. integrations/jetbrains/) or a companion repo.
  • Because the OKF core is .NET, the plugin should shell out to the okf CLI (or talk to the okf-mcp server) rather than reimplement OKF logic — keep one source of truth.
  • Minimum viable surface: run okf validate on the current bundle and surface diagnostics; a bundle/concept tree view.

Hard rules: this plugin is a separate, non-.NET project — it must not introduce any runtime dependency into src/OKF4net/ or src/OKF4net.Cli/, and must not modify tests/fixtures/. Decide clearly (in the discussion) whether it ships in-repo or as a companion repo.

How to verify: the plugin builds, loads in a Rider/IntelliJ sandbox instance, and its validate action reports the same diagnostics as okf validate on the same bundle.

Good to know: A validate-only MVP that shells out to the okf CLI is a great first cut. See CONTRIBUTING.md.

Dominant language
C#
Stars
4
Forks
1
Avg merge
1d 4h
Merged PRs (30d)
32

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jchable/okf4net

All issues in jchable/okf4net

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.