validating schema definitions

[KuceraMartin]

Should we allow Table objects to contain arbitrary fields/methods or not?

Currently we throw an exception when an unexpected field is encountered in the QueryBuilderFactory macro. Alternatively, we could just ignore these fields.

If we do want to be strict and only allow fields that translate to scope values, it would be nice if this checking happened at definition time and not when calling from(...). Ideally such that IDEs highlight the specific values in the object that are invalid. Could we somehow do this with macros? It would be cool if we could have a "custom case object", i.e. something like table object MyTable instead of case object MyTable extends Table

[KuceraMartin]

skip for now, later we could rethink whether we can validate at definition time

there was some master's thesis on triggering macros with annotations -> check the status of that