diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml index 0a4b0de7..7c52a342 100644 --- a/.github/workflows/gh-pages.yml +++ b/.github/workflows/gh-pages.yml @@ -1,12 +1,22 @@ name: Deploy to GitHub Pages -on: workflow_dispatch +on: + workflow_dispatch: + inputs: + branch: + type: choice + description: Which branch to deploy to peggyjs.org + required: true + options: + - stable jobs: deploy: runs-on: ubuntu-20.04 steps: - uses: actions/checkout@v3 + with: + ref: ${{ github.event.inputs.branch }} - name: Use Node.js 16.x uses: actions/setup-node@v3 with: diff --git a/docs/.eleventy.js b/docs/.eleventy.js index 77a72464..0b40977b 100644 --- a/docs/.eleventy.js +++ b/docs/.eleventy.js @@ -9,9 +9,7 @@ module.exports = function (eleventyConfig) { return { // Control which files Eleventy will process // e.g.: *.md, *.njk, *.html, *.liquid - templateFormats: ["html", "njk"], - // Process .html files with nunjucks - htmlTemplateEngine: "njk", + templateFormats: ["html", "njk", "liquid", "md"], // Path prefix for URLs pathPrefix: "/", // Config for input/output/data/etc. directories diff --git a/docs/documentation.html b/docs/documentation.html index c5a23010..0c30521e 100644 --- a/docs/documentation.html +++ b/docs/documentation.html @@ -157,7 +157,7 @@

Command Line

$ peggy arithmetics.pegjs

This writes parser source code into a file with the same name as the grammar -file but with “.js” extension. You can also specify the output file +file but with “.js” extension. You can also specify the output file explicitly:

$ peggy -o arithmetics-parser.js arithmetics.pegjs
@@ -562,16 +562,16 @@

Grammar Syntax and Semantics

first rule, which is also called the start rule.

A rule name must be a JavaScript identifier. It is followed by an equality -sign (“=”) and a parsing expression. If the rule has a human-readable name, it +sign (“=”) and a parsing expression. If the rule has a human-readable name, it is written as a JavaScript string between the rule name and the equality sign. Rules need to be separated only by whitespace (their beginning is easily -recognizable), but a semicolon (“;”) after the parsing expression is +recognizable), but a semicolon (“;”) after the parsing expression is allowed.

The first rule can be preceded by a global initializer and/or a per-parse initializer, in that order. Both are pieces of JavaScript -code in double curly braces (“{{'{{'}}” and “}}”) and single curly braces (“{” and -“}”) respectively. All variables and functions defined in both +code in double curly braces (“{{'{{'}}” and “}}”) and single curly braces (“{” and +“}”) respectively. All variables and functions defined in both initializers are accessible in rule actions and semantic predicates. Curly braces in both initializers code must be balanced.

The global initializer is executed once and only once, when the @@ -642,7 +642,7 @@

Grammar Syntax and Semantics

match result when parsing is successful.

One special case of parser expression is a parser action — a -piece of JavaScript code inside curly braces (“{” and “}”) that takes match +piece of JavaScript code inside curly braces (“{” and “}”) that takes match results of some of the the preceding expressions and returns a JavaScript value. This value is considered match result of the preceding expression (in other words, the parser action is a match result transformer).

@@ -721,9 +721,9 @@

Parsing Expressio

Match one character from a set and return it as a string. The characters in the list can be escaped in exactly the same way as in JavaScript string. The list of characters can also contain ranges (e.g. [a-z] - means “all lowercase letters”). Preceding the characters with ^ - inverts the matched set (e.g. [^a-z] means “all character but - lowercase letters”). Appending i right after the literal makes + means “all lowercase letters”). Preceding the characters with ^ + inverts the matched set (e.g. [^a-z] means “all character but + lowercase letters”). Appending i right after the literal makes the match case-insensitive.