Feature requests: allow for more than one example.
Input:
{"class": "101", "students": 101}
{"class": "201", "students": 80}
{"class": "202", "students": 50}
{"class": "301", "students": 120}
Example:
Class 101 has 101 students
Output:
Class 101 has 101 students
Class 201 has 201 students
Class 202 has 202 students
Class 301 has 301 students
Right now the first line cannot have any ambiguity. This is fixable by reordering, but with large enough data sets I may have some ambiguity in all lines, at different places. Multiple examples would fix that.
Again, loved the tool. I can see this going very far, specially with non-technical people.
For that use case you can use the Lapis[1][2] desktop app (the secret weapon I use for data munging), which allows you to choose several examples and edit a file with direct manipulation - or define patterns using a DSL.
You could just add a "dummy" input as the first line with all unique entries. Then just remove it from the output. Am I missing something? It's a tiny bit of additional manual processing, but doesn't seem unreasonable.
Right, but if you have a thousand items, with a dozen fields each, you can't be sure the one example you've picked will resolve all ambiguities. But if you could supply four or five example lines, the chances of ambiguity drop off.
Feature requests: allow for more than one example.
Right now the first line cannot have any ambiguity. This is fixable by reordering, but with large enough data sets I may have some ambiguity in all lines, at different places. Multiple examples would fix that.Again, loved the tool. I can see this going very far, specially with non-technical people.