Skip to content

ETL descriptions too long #1526

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 13, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions exercises/etl/canonical-data.json
Original file line number Diff line number Diff line change
@@ -1,19 +1,21 @@
{
"exercise": "etl",
"version": "1.0.0",
"version": "1.0.1",
"cases": [
{
"comments": [
"Transforms a set of legacy scrabble data stored as letters per score",
"to a set of data stored score per letter.",
"Note: The expected input data for these tests should have",
"integer keys (not stringified numbers as shown in the JSON below",
"Unless the language prohibits that, please implement these tests",
"such that keys are integers. e.g. in JavaScript, it might look ",
"like `transform( { 1: ['A'] } );`"
],
"description": "transforms the a set of scrabble data previously indexed by the tile score to a set of data indexed by the tile letter",
"description": "Transform legacy to new",
"cases": [
{
"description": "a single letter",
"description": "single letter",
"property": "transform",
"input": {
"1": ["A"]
Expand Down