-
Notifications
You must be signed in to change notification settings - Fork 0
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
Symbols instead of keywords? #30
Comments
I'd suggest just dispatching on |
emiln
pushed a commit
that referenced
this issue
Sep 23, 2015
Until now a command must start with a keyword. This has been relaxed and a command can now start with a keyword, a symbol, or a string. This means that all of the following are legal ways to represent a click: [click] [:click] ["click"] (click) (:click) ("click")
emiln
pushed a commit
that referenced
this issue
Sep 24, 2015
#30 Using a wrong command name will now produce an error message including the names of all currently implemented commands. This is fetched dynamically by inspecting the MultiFn and should always be up to date.
emiln
pushed a commit
that referenced
this issue
Sep 24, 2015
#30 The function to look up functions contained in a multimethod has been moved to a utils namespace and now sports a proper docstring.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I wonder if perhaps symbols would be easier for people to relate to for the EDN DSL. The current example in the README is
but it could just as easily be
or even
The text was updated successfully, but these errors were encountered: