Details
Description
Little language example:
((suite = "smoke" | suite = "regression") & process = "booking")
Groovy closures (http://groovy.codehaus.org/Quick+Start) would be an effective way to construct an alternate grammar.
It should be a non-default implementation to allow for backwards compatibility.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | meta-filter (command line) needs a proper albeit little language | MetaFilter should support logic written in a scripting language |
| Assignee | Mauro Talevi [ maurotalevi ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Assignee | Mauro Talevi [ maurotalevi ] | Paul Hammant [ paul ] |
| Resolution | Fixed [ 1 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Summary | MetaFilter should support logic written in a scripting language | MetaFilter should support meta matching logic written in a Groovy |
| Fix Version/s | 3.5.4 [ 18081 ] | |
| Description |
Little language example:
((suite = "smoke" | suite = "regression") & process = "booking") It could be that Groovy closures (http://groovy.codehaus.org/Quick+Start) or Rhino (http://www.mozilla.org/rhino/tutorial.html) could be an effective way to construct an alternate grammar. Having this as a plugin -DmetaFilterImplementation might allow for backwards compatibility too. |
Little language example:
((suite = "smoke" | suite = "regression") & process = "booking") Groovy closures (http://groovy.codehaus.org/Quick+Start) would be an effective way to construct an alternate grammar. It should be a non-default implementation to allow for backwards compatibility. |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
We could introduce a prefix-based convention for different language impls. E.g.: "groovy: ((suite = "smoke" | suite = "regression") & process = "booking")".
This would keep the meta-filter nice and compact, a single string rather than depending on additional settings.