frictionlessdata / datapackage-js / 55

89%

push

travis-ci

[BREAKING] Rebased on updated codebase (#7)

* Setup repository (#5)

* Remove tests

* Copy jsontableschema-js skeleton

* Add .idea/

* Use jsontableschema-js scripts and deps

* Update template, add badges, add note about the API changes

* Add testing data previously found in test/fixtures #<a class=hub.com/frictionlessdata/datapackage-js/commit/6366ce930b9085081b3ff275fb3af65a0829cff6">6366ce930

* Stub code for passing the tests

* Add babel and mocha configs

* Stub test

* Stub index for the build scripts

* Add lodash as dependency

* Added Resource class (#10)

* Remove tests

* Copy jsontableschema-js skeleton

* Add .idea/

* Use jsontableschema-js scripts and deps

* Update template, add badges, add note about the API changes

* Add testing data previously found in test/fixtures #6366ce930b9085081b3ff275fb3af65a0829cff6

* Stub code for passing the tests

* Add babel and mocha configs

* Stub test

* Stub index for the build scripts

* Add lodash as dependency

* Add jts and nock as dependencies

* Initial Resource implementation

* Initial tests for the Resource implementation

* Use js getters

* Rename _getResourceField to _getSourceKey

* Use the source getter in get table

* Add transform-async-to-generator

* Use await instead of then on resource.table

* Add docstrings

* Add babel-plugin-transform-async-to-generator

* Add tests that work on dp1 from data/

* table getter discards errors and resolves in null, make sourceKey getter

* Add test to make resource.table resolves in null

* Add test for resource.table with csv file

* Move test data to test directory

* Move test data to data/ directory

* Rename sourceKey to _sourceKey, reject rejected jts.Table with null

* Test on actual data from csv file, expect rejected table to be null

* Add simple caching for jts.Table and make it resolve to null on errors

* Expect table promise to resolve to null on errors

* Setup eslint (#18)

* Remove tests

* Copy... (continued)

225 of 225 new or added lines in 6 files covered. (100.0%)

211 of 225 relevant lines covered (93.78%)

21.21 hits per line