[
https://issues.apache.org/jira/browse/METRON-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297256#comment-16297256
]
ASF GitHub Bot commented on METRON-1339:
----------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/856
Why is this validation process driven by a %magic command?
Magics were made for functionality that cannot be implemented directly
within a Stellar execution environment. Often for answering questions 'about'
the execution environment itself. For example `%vars` or `%functions` or
`%globals` all tell us about the Stellar execution environment.
This logic doesn't seem like a good fit for a %magic, unless there is a
limitation that I am not understanding. This could be implemented, I would
argue more simply, as a regular Stellar function.
> Stellar Shell: Should have a way to validate deployed functions
> ---------------------------------------------------------------
>
> Key: METRON-1339
> URL: https://issues.apache.org/jira/browse/METRON-1339
> Project: Metron
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> It is possible that the Stellar Language is changed during a release, meaning
> stellar expressions that are in zookeeper are now invalid, and will not run.
> Currently users cannot verify this without just letting them fail and hunting
> the errors down.
> The Stellar Shell should expose a '%' function that will verify that all
> stellar functions compile and are syntactically correct.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
