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.
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):
integrations/jetbrains/) or a companion repo.okfCLI (or talk to theokf-mcpserver) rather than reimplement OKF logic — keep one source of truth.okf validateon 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/orsrc/OKF4net.Cli/, and must not modifytests/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 validateon the same bundle.Good to know: A validate-only MVP that shells out to the
okfCLI is a great first cut. See CONTRIBUTING.md.