Examples from the README
example 1
[
{ "let": { "name": "JSON", "times": 3 } },
{
"for": {
"var": "i",
"from": 1,
"to": "times",
"do": [
{ "print": { "add": ["Hello ", "name"] } }
]
}
}
]
example 2
[
{ "import": "system.jpl" },
{ "print": { "call": { "now": [] } } },
{ "print": { "call": { "osName": [] } } },
{ "print": { "call": { "cpuCount": [] } } },
{ "let": { "a": 9, "b": 4, "name": "JPL" } },
{ "print": { "add": ["\"a + b = \"", { "add": ["a", "b"] }] } },
{ "print": { "mul": ["a", "b"] } },
{ "print": { "div": ["a", "b"] } },
{ "print": { "mod": ["a", "b"] } },
{ "print": { "&": [6, 3] } },
{ "print": { "||": [false, true] } },
{ "print": { "gt": ["a", "b"] } },
{ "def": { "sq": { "params": ["x"], "body": [{ "return": { "mul": ["x", "x"] } }] } } },
{ "print": { "call": { "sq": [5] } } },
{ "def": { "greet": { "params": ["who"], "body": [{ "return": { "add": ["\"Hi, \"", "who"] } }] } } },
{ "print": { "call": { "greet": ["\"JSON Fan\""] } } },
{ "if": { "cond": { "<": ["b", "a"] }, "then": { "print": "\"b < a 👍\"" }, "else": { "print": "\"b >= a 🤔\"" } } },
{ "for": { "var": "i", "from": 1, "to": 3, "step": 1, "do": [ { "print": { "call": { "sq": ["i"] } } } ] } },
{ "print": "\"All features in one! 🎉\"" }
]
example 3
[
// 🚀 Welcome to JPL — JSON Programming Language!
// Import system utilities for fun stuff
{ "import": "system.jpl" },
// Print system info
{ "print": { "call": { "now": [] } } },
{ "print": { "call": { "osName": [] } } },
{ "print": { "call": { "cpuCount": [] } } },
// Define a math function to square a number
{
"def": {
"square": {
"params": ["x"],
"body": [
{ "return": { "mul": ["x", "x"] } }
]
}
}
},
// Greet a user
{
"def": {
"greet": {
"params": ["name"],
"body": [
{ "return": { "add": ["Hello, ", "name"] } }
]
}
}
},
// Declare variables
{ "let": { "a": 7, "user": "Kapil" } },
// Use greet function and print
{ "print": { "call": { "greet": ["user"] } } },
// Conditional message
{
"if": {
"cond": { ">": ["a", 5] },
"then": { "print": "a is greater than 5" },
"else": { "print": "a is 5 or less" }
}
},
// Loop with break and continue
{
"for": {
"var": "i",
"from": 1,
"to": 10,
"step": 1,
"do": [
{ "if": { "cond": { "eq": ["i", 3] }, "then": { "continue": true } } },
{ "if": { "cond": { "gt": ["i", 7] }, "then": { "break": true } } },
{ "print": { "call": { "square": ["i"] } } }
]
}
},
// Fun ending message
{ "print": "🎉 Done with curly braces and JSON fun!" }
]
In non-minimal changesets, I would miss information/documentation about individual logical changes that make up the changeset. Commit separation that is useful for review will also be useful for history.
I prefer a deliberate, rebase- and rewrite-heavy workflow with a semi-linear history. The linear history remains readable, while allowing sum-of-parts changesets/merges.
It's an investment, but I think it guides into good structuring and thoughts, and whenever you look at history, you have more than a squashed potential mess.
Squash-on-merge is simpler to implement and justify, of course. Certainly much better than "never rebase, never rewrite, always merge", which I am baffled some teams have no problem doing. The history tree quickly becomes unreadable.