660
94%
master: 81%

Ran 23 Feb 2018 07:44PM UTC

Jobs 5

Files 41

Run time 41s

Badge

Embed ▾

pending completion

Build # 660

Build Type

push

travis-ci

Committed by

vitorbaptista

Commit Message

[#251] Allow non-required primary keys

If a field is a `primaryKey`, we validate that it exists, the same way as if it
had `{'constraints': {'required': True}}`. However, there can be some cases
where a `primaryKey` field can be null. Pretty uncommon, but messy data...

This commit allows removing the check by explicitly setting the `required` to
False, so a field like:

```
"fields": [
  {
    "name": "id",
    "constraints": {
      "required": False
    }
  }
],
"primaryKey": "id"
```

Wouldn't be required. In other words, the `required` constraint overloads the
`primaryKey` constraint.

Fixes #251

Run Details

1144 of 1223 relevant lines covered (93.54%)

3.74 hits per line

Jobs

ID	Job ID	Ran	Coverage
1	660.1	23 Feb 2018 07:45PM UTC	93.54	Travis Job 660.1
2	660.2	23 Feb 2018 07:45PM UTC	93.54	Travis Job 660.2
3	660.3	23 Feb 2018 07:45PM UTC	93.54	Travis Job 660.3
4	660.4	23 Feb 2018 07:44PM UTC	93.46	Travis Job 660.4
5	660.5 (TOXENV=lint)	23 Feb 2018 07:44PM UTC		Travis Job 660.5

Source Files on build 660

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

frictionlessdata / goodtables-py / 660
94%
master: 81%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 660

frictionlessdata / goodtables-py / 660 94% master: 81%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 660

frictionlessdata / goodtables-py / 660
94%
master: 81%

README BADGES
x