FEEL language tooling

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

Nico Rehwaldt 2023

Disclaimer*

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

2

Background

3

4

5

6

7

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

8

Language tooling?

9

Text editor demo :frame_with_picture:

10

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

Modelers should deeply integrate the language tooling.

11

FEEL editing demo :frame_with_picture:

12

Baseline (any language)

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

Advanced (FEEL)

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

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

15

Feel templating demo :frame_with_picture:

16

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

➡️ Solution acceleration; foundation for advanced features.
17

Strategy* Embrace FEEL. Make additional language tooling pluggable.

Provide building blocks and establish best practices.
18

Thanks

❤️

19

Appendix

20

Why FEEL?

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

Building blocks

22