lux icon indicating copy to clipboard operation
lux copied to clipboard

Illogical intents have inconsistent errors

Open willeppy opened this issue 4 years ago • 0 comments

Hi,

If I specify an illogical intent, i.e. one where the conditions do not overlap or make sense like specifying an attribute that is a quantitative variable but then also specifying that my data_type is nominal this leads to different kinds of error, depending on the inconsistency.

Im using the data in lux-binder, notebook 1-specifying-intent.ipynb as an example.

Example one where attribute and data_type don't match

error 1

Example two where attribute and data_model don't match

error 2

In both of these cases the intent doesn't really make any sense but the error handling is different. There could be other cases with different clause parameters but I haven't experimented with all of them.

Also not sure what the best solution is in terms of showing empty vis or giving an error. One way to solve would be to do more thorough input validation for inconsistencies maybe.

willeppy avatar Feb 21 '21 04:02 willeppy