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

Dynamic data type for @Configured properties where value is provided by either InputColumn or some enumerable setting #6

Open
kaspersorensen opened this issue Feb 20, 2014 · 0 comments

Comments

@kaspersorensen
Copy link
Member

For quite a lot of analyzers we could use a smarter way to configure in situations where input can either be provided in a fixed form (typically an enum) or be dynamic based on input column values.

For instance: Any aggregation could be based on record count (fixed "1" value) or based on some count in a column. To support both options, you would typically provide two @configured properties, leading to a confusion since the user has to decide on one rule using two separate properties.

A rough/initial proposal could be like this:

enum MyOption {
  RECORD_COUNT
}

@Configured
DynamicOption<MyOptions, Number> count;

...

MyOption countOption = count.getEnumValue()
InputColumn<Number> countInputColumn = count.getInputColumn();
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant