Categorize built-ins / expose reserved name built-ins

README.md

@@ -14,6 +14,15 @@ npm install @camunda/feel-builtins
 
 ## Usage
 
+This package exports multiple collections of FEEL builtins:
+
+* **`camundaBuiltins`**: Collection of builtins of camunda scala FEEL.
+* **`feelBuiltins`**: List of standard FEEL built-in functions (excluding Camunda-specific extensions).
+* **`camundaExtensions`**: List of FEEL camunda extensions.
+* **`camundaReservedNameBuiltins`**: Functions using reserved keywords in their name and need to be added to the parser context during parsing.
+
+You can feed built-ins as context into your favorite [FEEL editor](#feel-editor) or [validator](#feel-lint).
+
 ### Feel Editor
 
 In your [FEEL editor](https://github.com/bpmn-io/feel-editor) you can use these builtins to establish the Camunda context:
@@ -29,6 +38,17 @@ const editor = new FeelEditor({
 });
 ```
 
+If you only want standard FEEL functions, use `feelBuiltins` instead:
+
+```js
+import { feelBuiltins } from '@camunda/feel-builtins';
+
+const editor = new FeelEditor({
+  container,
+  builtins: feelBuiltins
+});
+```
+
 ### Feel Lint
 
 With [@bpmn-io/feel-lint](https://github.com/bpmn-io/feel-lint) you can also use the builtins to lint expressions in the Camunda world:

dist/index.d.ts

@@ -1,7 +1,24 @@
 /**
- * A collection of builtin of FEEL.
+ * Collection of builtins of camunda scala FEEL.
  */
 export const camundaBuiltins: Builtin[];
+
+/**
+ * List of standard FEEL built-in functions (excluding Camunda-specific extensions).
+ */
+export const feelBuiltins: Builtin[];
+
+/**
+ * List of FEEL camunda extensions.
+ */
+export const camundaExtensions: Builtin[];
+
+/**
+ * Camunda built-ins that use reserved keywords in their name and thus must
+ * be explicitly declared when parsing FEEL.
+ */
+export const camundaReservedNameBuiltins: Builtin[];
+
 export type Builtin = {
   /**
    * The name of the builtin function.
@@ -12,11 +29,11 @@ export type Builtin = {
    */
   info: string;
   /**
-   * type of the builtin, always 'function' for builtin functions.
+   * Type of the builtin, always 'function' for builtin functions.
    */
-  type?: "function";
+  type?: 'function';
   /**
-   * function parameters.
+   * Function parameters.
    */
   params?: Array<{
     name: string;

package.json

@@ -16,6 +16,7 @@
     "compile-builtins": "node tasks/compileBuiltins.js"
   },
   "devDependencies": {
+    "@bpmn-io/lezer-feel": "^2.2.1",
     "@types/chai": "^5.2.2",
     "@types/mocha": "^10.0.10",
     "@types/node": "^24.0.0",