FEEL language tooling

Imagining the future of editing support in Camunda and how we get there.

Nico Rehwaldt

Disclaimer*

This is a pitch and does not imply any current or future development direction. 🤞

Background

Investing into (FEEL) language tooling will make our (low-code) users more successful in process orchestration.

Language tooling?

Text editor demo 🖼️

Our users should not require external editors to do the job.

Modelers should deeply integrate the language tooling.

FEEL editing demo 🖼️

Baseline (any language)

• Monospace
• Syntax highlighting
• Common keyboard shortcuts
• Smart indent
• Completions ❓

Advanced (FEEL)

• Deep understanding of the language
• Contextual completion (i.e. based on available data)

We want to start with FEEL language tooling and embrace it's use across the stack.

Feel templating demo 🖼️

Mission* Make our users more successful in process orchestration through state-of-the-art language tooling.

➡️ Solution acceleration; foundation for advanced features.

Strategy* Embrace FEEL. Make additional language tooling pluggable.

Provide building blocks and establish best practices.

Thanks

❤️

Appendix

Why FEEL?

• FEEL is defined as part of the DMN specification
• It is the scripting language in Camunda 8
• It is simple, and powerful 😉

Building blocks

• CodeMirror recommended as foundation
• Pluggable language support
• Grammar and language definitions for FEEL
• An embeddable FEEL editor
• Extensible variable resolver
• ...