• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

mrodrig / json-2-csv / 7983786658 / 2
98%
stable: 98%

Build:
Build:
LAST BUILD BRANCH: fix-277
DEFAULT BRANCH: stable
Ran 21 Feb 2024 04:01AM UTC
Files 5
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Feb 2024 03:59AM UTC coverage: 97.906% (+0.02%) from 97.884%
7983786658.2

Pull #246

github

mrodrig
fix: resolve potential excludeKeys match to a key path other than at the start of a string

In a case where `excludeKeys` is set to `["arr"]`, there was a possibility that with JSON data looking like this:

```
[
    {
        "id": 1,
        "arr": [
            {
                "name": "foo"
            }
        ],
        "name": {
            "arr": "this should appear"
        }
    },
    {
        "id": 2,
        "arr": [
            {
                "name": "bar"
            }
        ],
        "name": {
            "arr": "this should also appear"
        }
    }
]
```

could potentially result in both `arr.name` and `name.arr` being excluded. By adjusting the RegExp thats being used for the matching, this fixes a potential bug that caused `name.arr` to be mistakenly excluded.
Pull Request #246: Feat/improved exclude keys matching

264 of 269 branches covered (98.14%)

374 of 382 relevant lines covered (97.91%)

276.05 hits per line

Source Files on job node-Linux-21 - 7983786658.2
  • Tree
  • List 0
  • Changed 3
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 7983786658
  • e18d66c7 on github
  • Prev Job for on feat/improved-excludeKeys-matching (#6688044778.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc