Manifold Cheat Sheet

IntelliJ IDEA

Manifold is best experienced in IntelliJ IDEA. The Manifold plugin provides comprehensive support for IntelliJ features including code completion, navigation, usage searching, refactoring, incremental compilation, hotswap debugging, full-featured ManTL template editing, and more.

Install the plugin directly from IntelliJ:

SettingsPluginsMarketplace ➜ search: Manifold

Sample Projects

Clone the Manifold sample project to for a nice demonstration of features.

Clone the Manifold sample GraphQL project to learn more about schema-first design with GraphQL using Manifold.

Clone the Manifold sample REST API project to quickly begin experimenting with a JSON Schema REST API using Manifold.

Clone the Manifold sample Web App project to get hooked on ManTL templates with the Manifold IntelliJ plugin.



Gain direct, type-safe access to any type of data. Remove the code gen step in your build process.


Put data files in your resource path.

A typical Maven setup:

-- main
---- java
------ <your .java files>
---- resources
------ <your .png, .json, .graphql, .mtl, and other resource files>

JSON & JSON Schema

You can use both sample JSON files and JSON Schema files.


  "Name": "Joe Jayson",
  "Age": 39,

Use Person.json as a JSON-by-example schema:

import abc.Person;
Person person = Person.fromJsonUrl(url);

Or use JSON Schema files: resources/abc/Contact.json Here is a simple User type defined in resources/abc/User.json using JSON Schema:

  "$schema": "",
  "$id": "",
  "type": "object",
  "definitions": {
    "Gender": {
      "type": "string",
      "enum": ["male", "female"]
  "properties": {
    "name": {
      "type": "string",
      "description": "User's full name.",
      "maxLength": 80
    "email": {
      "description": "User's email.",
      "type": "string",
      "format": "email"
    "date_of_birth": {
      "type": "string",
      "description": "Date of uses birth in the one and only date standard: ISO 8601.",
      "format": "date"
    "gender": {
      "$ref" : "#/definitions/Gender"
  "required": ["name", "email"]

You can use this to create a new instance of the User type and then modify it using setter methods to change optional properties:

import abc.User;
import abc.User.Gender;
import java.time.LocalDate;
User user = User.create("Scott McKinney", "");
user.setDate_of_birth(LocalDate.of(1980, 7, 4));

Alternatively, you can use builder() to fluently build a new instance:

User user = User.builder("Scott McKinney", "")
  .withDate_of_birth(LocalDate.of(1980, 7, 4))

You can load a User instance from a String:

// From a YAML string
User user = User.load().fromYaml(
  "name: Scott McKinney\n" +
  "email:\n" +
  "gender: male\n" +
  "date_of_birth: 1980-07-04"

Load from a file:

// From a JSON file
User user = User.load().fromJsonFile("/path/to/MyUser.json");

You can invoke a REST API to fetch a User using HTTP GET:

// Uses HTTP GET to invoke the API
User user = User.load().fromJsonUrl("$userId");

Request REST API services

Use the request() static method to conveniently navigate an HTTP REST API with GET, POST, PUT, PATCH, & DELETE:

String id = "scott";
User user = User.request("").getOne("/$id");

The request() method provides support for all basic REST API client usage:

Requester<User> req = User.request("");

// Get all Users via HTTP GET
IJsonList<User> users = req.getMany();

// Add a User with HTTP POST
User user = User.builder("scott", "mypassword", "Scott")

// Get a User with HTTP GET
String id = user.getId();
user = req.getOne("/$id");

// Update a User with HTTP PUT
user.setDob(LocalDate.of(1980, 7, 7));
req.putOne("/$id", user);

// Delete a User with HTTP DELETE

Clone the Manifold sample REST API project to quickly begin experimenting with a JSON Schema REST API using Manifold.

Writing JSON

An instance of a JSON API object can be written as formatted text with write():

The following example produces a JSON formatted string:

User user = User.builder("Scott McKinney", "")
  .withDate_of_birth(LocalDate.of(1980, 7, 4))

String json = user.write().toJson();


  "name": "Scott McKinney",
  "email": "",
  "gender": "male",
  "date_of_birth": "1980-07-04"


Manifold fully supports YAML 1.2. You can use YAML to build JSON Schema files as well. All that applies to JSON applie to YAML.


Avoid strings, access properties type-safely:


chocolate = Chocolate
chocolate.milk = Milk chocolate
chocolate.dark = Dark chocolate
String myMessage = MyProperties.chocolate.milk;


Gain direct type-safe access to all your project’s images, efficiently cached:


import abc.images.*;
ImageIcon image = companyLogo_png.get();



var x = 1;

function nextNumber() {
  return x++;

function doSomething(x) {
  return x + " from Javascript";

A JavaScript file and its members are directly accessible as a Java class:

import abc.MyJsProgram;
String hello = MyJsProgram.doSomething("Hello");
System.out.println(hello); // prints 'Hello from JavaScript'

double next = JsProgram.nextNumber();
System.out.println(next); // prints '1'

String Templates (string interpolation)


By default String templates are disabled. Enable the feature with the strings Manifold plugin argument.


  <arg>-Xplugin:Manifold strings</arg>


A String template lets you use the $ character to embed a Java expression directly into a String. You can use $ to embed a simple variable:

int hour = 8;
String time = "It is $hour o'clock";  // prints "It is 8 o'clock"

Or you can embed an expression of any complexity in curly braces:

LocalTime localTime =;
String ltime = "It is ${localTime.getHour()}:${localTime.getMinute()}"; // prints "It is 8:39"

Escape the $ with \$.

Use @DisableStringLiteralTemplates to turn string templates off at the class and method levels.



Add your own methods to any class e.g., java.lang.String:

Make a class in a package named extensions. Create a sub-package using the full name of the class you want to extend, in this case java.lang.String:


import manifold.ext.api.*;

public class MyStringExtension {

  public static void print(@This String thiz) {

  @Extension // required for static extension methods
  public static String lineSeparator() {
    return System.lineSeparator();

Now the methods are available directly from String:

String hello = "hello";

// static method


Here map is a generic extension method on Collection having type variable R and conveying Collection’s type variable E. Extension methods must reflect the type variable names declared in the extended class.

public static <E, R> Stream<R> map(@This Collection<E> thiz, Function<? super E, R> mapper) {

@Structural - Structural Interfaces

Unify disparate APIs. Bridge software components you do not control. Access maps through type-safe interfaces.

public interface Coordinate {
  double getX();
  double getY();

Structural interface applied to java.awt.Rectangle:

setLocation((Coordinate)new Rectangle(10, 10, 100, 100));
void setLocation(Coordinate location) {
  this.location = location;

Structural interface applied to java.util.HashMap via ICallHandler:

Map<String,Integer> map = new HashMap<>();
map.put("x", 10);
map.put("y", 10);

Coordinate coord = (Coordinate)map;
double x = coord.getX();

@Jailbreak - Type-safe Reflection

Access private features with @Jailbreak to avoid the drudgery and vulnerability of Java reflection.


@Jailbreak Foo foo = new Foo(1);
foo._privateField = 88;
public class Foo {
  private final int _privateField;
  public Foo(int value) {
    _privateField = value;
  private String privateMethod() {
    return "hi";
  private String privateMethod(String param) {
    return param;

Static Members

@Jailbreak MyClass myClass = null; // value is insignificant
myClass.Static_Field = "hi";
public class MyClass {
  private static String Static_Field = "hello";
  private static void staticMethod() {

Types and Constructors @Jailbreak SecretClass secretClass = 
  new @Jailbreak SecretClass("hi");
secretClass._data = "hey";

@Self - The Self Type

Manifold supports the Self type via the @Self annotation. Use @Self with method return types, parameter types, and field types to enforce subtype of this where suitable. Use @Self as a simpler, more versatile alternative to Java’s recursive generic types.


You can use @Self to make methods like equals() type-safe:

public class MyClass {
  public boolean equals(@Self Object obj) {

Now your equals() method enforces MyClass as the parameter:

myClass.equals("notMyClass"); // Compile Error. :)


A common use-case for the Self type involves fluent APIs like the Builder pattern:

public class VehicleBuilder {
  private int _wheels;

  public VehicleBuilder withWheels(int wheels) {
    _wheels = wheels;
    return this; // returns THIS

This is fine until we subclass it:

public class AirplaneBuilder extends VehicleBuilder {
  private int _wings;

  public AirplaneBuilder withWings(int wings) {
    _wings = wings;
    return this; // returns THIS


Airplane airplane = new AirplaneBuilder()
  .withWheels(3) // returns VehicleBuilder :(
  .withWings(1)  // ERROR

withWheels() returns VehicleBuilder, not AirplaneBuilder. This is a classic example where we want to return the “the subtype of this. This is what the self type accomplishes:

  public @Self VehicleBuilder withWheels(int wheels) {
    _wheels = wheels;
    return this; // returns THIS

Now with the return type annotated with @Self the example works as desired:

Airplane airplane = new AirplaneBuilder()
  .withWheels(2) // returns AirplaneBuilder :)
  .withWings(1)  // GOOD!

Annotate with @Self to preserve the “the subtype of this anywhere on or in a method return type, parameter type, or field type.

Self + Generics

You can also use @Self to annotate a type argument. A nice example of this involves a typical graph or tree structure where the nodes in the structure are homogeneous:

public class Node {
  private List<Node> children;

  public List<@Self Node> getChildren() {
    return children;

  public void addChild(@Self Node child) {

public class MyNode extends Node {

Here you can make the component type of List the Self type so you can use the getChildren method type-safely from subtypes of node:

MyNode myNode = findMyNode();
List<MyNode> = myNode.getChildren(); // wunderbar!

Self + Extensions

You can use @Self with extension methods too. Here we make an extension method as a means to conveniently chain additions to Map while preserving its concrete type:

public static <K,V> @Self Map<K,V> add(@This Map<K,V> thiz, K key, V value) {
  thiz.put(key, value);
  return thiz;

HashMap<String, String> map = new HashMap<>()
  .add("nick", "grouper")
  .add("miles", "amberjack");
  .add("alec", "barracuda")

Overriding Methods

Using @Self in a method return type or parameter type has no effect on the method’s override characteristics or binary signature:

public class SinglyNode {
  private @Self SinglyNode next;

  public void setNext(@Self SinglyNode next) { = next;

public class DoublyNode extends SinglyNode {
  private @Self DoublyNode prev;

  public void setNext(@Self SinglyNode next) {
    if(next instanceof DoublyNode) {
      ((DoublyNode)next).prev = this;
    else {
      throw new IllegalArgumentException();

Checked Exception Suppression

Simply add the exceptions plugin argument: -Xplugin:Manifold strings exceptions. Now checked exceptions behave like unchecked exceptions! No more compiler errors, no more boilerplate try/catch nonsense.

List<String> strings = ...;
List<URL> urls = list
  .map(URL::new) // No need to handle the MalformedURLException!

To use Checked Exception Suppression you must add the exceptions plugin option to your build configuration.



      <!-- Add the Manifold plugin, with string templates and checked exception suppression enabled -->
      <arg>-Xplugin:Manifold strings exceptions</arg>



tasks.withType(JavaCompile) { // Add the Manifold plugin, with string templates and checked exception suppression enabled options.compilerArgs += ‘-Xplugin:Manifold strings exceptions’ options.fork = true }


If your IntelliJ project is NOT defined with Maven or Gradle, you can add the plugin arguments in the Settings window e.g., SettingsBuild, Execution, DeploymentCompilerJava CompilerAdditional command line parameters: -Xplugin:"Manifold strings exceptions" -processorpath /path/to/your/manifold-all-xxx.jar

Note the -processorpath argument is required for Java 9 and later, not Java 8.

ManTL (Superfast type-safe templates)

ManTL has a separate cheat sheet


Leverage stock Manifold extension libraries for standard Java classes. Save time and reduce boilerplate code.

File file = new File(path);
// Use refreshing extensions to File
String content = file.readText();

Use the manifold-all dependency to access all Manifold’s provided extension libraries including I/O, Web, and Collections.

Learn More