Add JFLEG
{'login': 'j-chim', 'id': 22435209, 'node_id': 'MDQ6VXNlcjIyNDM1MjA5', 'avatar_url': 'https://avatars.githubusercontent.com/u/22435209?v=4', 'gravatar_id': '', 'url': 'https://api.github.com/users/j-chim', 'html_url': 'https://github.com/j-chim', 'followers_url': 'https://api.github.com/users/j-chim/followers', 'following_url': 'https://api.github.com/users/j-chim/following{/other_user}', 'gists_url': 'https://api.github.com/users/j-chim/gists{/gist_id}', 'starred_url': 'https://api.github.com/users/j-chim/starred{/owner}{/repo}', 'subscriptions_url': 'https://api.github.com/users/j-chim/subscriptions', 'organizations_url': 'https://api.github.com/users/j-chim/orgs', 'repos_url': 'https://api.github.com/users/j-chim/repos', 'events_url': 'https://api.github.com/users/j-chim/events{/privacy}', 'received_events_url': 'https://api.github.com/users/j-chim/received_events', 'type': 'User', 'site_admin': False}
[]
[]
Hi @j-chim ! You're right it does feel redundant: your option works better, but I'd even suggest having the references in a Sequence feature, which you can declare as:
```
	    features=datasets.Features(
                {
                    "sentence": datasets.Value("string"),
                    "corrections": datasets.Sequence(datasets.Value("string")),
                }
            ),
```

To create the dummy data, you just need to tell the generator which files it should use, which you can do with:
`python datasets-cli dummy_data datasets/<your-dataset-folder> --auto_generate --match_text_files "train*,dev*,test*"`
 Many thanks for this @yjernite! I've incorporated your feedback and sorted out the dummy data.
This PR adds [JFLEG ](https://www.aclweb.org/anthology/E17-2037/), an English grammatical error correction benchmark. 

The tests were successful on real data, although it would be great if I can get some guidance on the **dummy data**. Basically, **for each source sentence there are 4 possible gold standard target sentences**. The original dataset comprise files in a flat structure, labelled by split then by source/target (e.g., dev.src, dev.ref0, ..., dev.ref3). Not sure what is the best way of adding this.

I imagine I can treat each distinct source-target pair as its own split? But having so many copies of the source sentence feels redundant, and it would make it less convenient to end-users who might want to access multiple gold standard targets simultaneously. 
{'url': 'https://api.github.com/repos/huggingface/datasets/issues/1144/reactions', 'total_count': 0, '+1': 0, '-1': 0, 'laugh': 0, 'hooray': 0, 'confused': 0, 'heart': 0, 'rocket': 0, 'eyes': 0}
{'url': 'https://api.github.com/repos/huggingface/datasets/pulls/1144', 'html_url': 'https://github.com/huggingface/datasets/pull/1144', 'diff_url': 'https://github.com/huggingface/datasets/pull/1144.diff', 'patch_url': 'https://github.com/huggingface/datasets/pull/1144.patch', 'merged_at': '2020-12-06T18:16:04Z'}