JetBrains on Quentin's blog

How to enable JSON or YAML validation with JSON Schemas in IntelliJ

Sat, 03 Jan 2026 00:00:00 +0000

This is another article about plugin development for IntelliJ-based IDEs. In this article, I am describing how to implement some support for JSON or YAML files using a JSON Schema. While the JSON support is expected, the YAML support is a bit more surprising. It is possible because JSON and YAML are very similar formats, YAML 1.2 even being a superset of JSON.

I recently implemented that trick in my plugin FHIR® and SUSHI Support to provide a better experience while working with a specific YAML file (the sushi-config.yaml file). I discovered that neat feature in the YAML documentation, but I had to use the IntelliJ Platform Explorer to discover how a plugin could register a new JSON Schema in the IDE. That topic isn't covered by the IntelliJ Platform SDK Documentation documentation, so I am sharing my findings here.

Implement syntax highlighting of a new language in JetBrains IDEs

Mon, 18 Mar 2024 00:00:00 +0000

I regularly spend time working on FHIR ImplementationGuides, and I use the Visual Studio Code IDE to develop them. It is an IDE I used to work with, but as of lately, my preference goes to the Jetbrains IDEs.

The FHIR ImplementationGuides are written in a mix of Markdown, HTML, XML, JSON, INI and a specific language called FHIR Shorthand (FSH). While the former languages are properly supported in many IDEs, the latest is only supported in Visual Studio Code through a dedicated extension.

Improving performance of the IG Publisher: I/O operations

Thu, 11 Jan 2024 00:00:00 +0000

The IG Publisher is the reference tool to build FHIR implementation guides. It is a Java application built upon the FHIR Core library, that reads the implementation guide sources and generates a FHIR package and a web documentation. It is a quite complex application, and new versions are released quite regularly.

I recently had to build a large implementation guide, and it took the IG Publisher around 3 hours to complete. The memory usage was quite high (around 20 GiB at peak) and the result was a 2.57 GiB directory. While waiting for the completion, I was wondering if there was a way to reduce the completion time.