Thad Guidry

I would prefer just adding them to a approved list. We might even want to expose that approved list as a user configurable preference with initial sensible defaults.

Even better would be to know during GREL parsing that the Object is an Array having the .filter() function applied and completely avoiding the variable passing of `vC`. Concisely: `cell.recon.candidates.filter(score...

It's something we discussed during the early days of GREL design... just thought I would mention it. :-)

Well for filter() that might have to change to be just a regular function, if my hunch is right after 4.0 :-) We'll have to discuss this while toying with...

Closing issue as won't fix since it's a fundamental change to our Control versus Function handling and only a syntactic convenience.

Hmm, this might fit into one of the issues/stories off of this Epic. https://rumbledb.org/ Putting it under Querying for now @wetneb Hmm, have you seen it or heard of it?...

@wetneb Hmm, Validation (JSON Schema issue like you created, etc.) probably needs to fit into the big picture here somewhere. At import time, I can see someone using OpenRefine to...

@tfmorris Records mode (fields grouped with values) currently in OpenRefine is used myriad of ways; I know this because I myself use it in ways not even Records based, but...

@tfmorris Do a search on "records" in our issues. https://github.com/OpenRefine/OpenRefine/issues?q=is%3Aissue+is%3Aopen+record Collecting them and organizing the use cases into this EPIC is what I've been trying to do. The tech examples...

**Added**: Transforming sub data sometimes in arrays into columns/fields of a record #36