Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settle on expression language #1

Open
nicpottier opened this issue Sep 9, 2016 · 1 comment
Open

Settle on expression language #1

nicpottier opened this issue Sep 9, 2016 · 1 comment

Comments

@nicpottier
Copy link
Contributor

We use a library we built which is simple Excel inspired functions:
https://github.com/rapidpro/expressions

Our thoughts are basically just:

  • no looping should be supported
  • no complicated control structures
  • but basic math / date / string functions are useful
@nicpottier
Copy link
Contributor Author

Note that a chosen expression language is probably separate than how templating will be handled, but worth considering at the same time.

RapidPro does:

Hi @contact.name

Just because having only a leading character seems to be easier for users to grock (as opposed to ${contact.name} and lets us do decent completion. The more advanced case of:

Hi @(CAMELCASE(contact.name)) 

(to call a function) is slightly more awkward but also not used as often. (and still allows completion)

CC: @ericnewcomer @rowanseymour

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant