Make it easier to determine which feed resulted in invalid JSON

Open on Drupal.org →

Created on 18 August 2021, over 3 years ago

Updated 23 April 2024, about 1 year ago

Problem/Motivation

The following code prints out the feed from which invalid json was emitted.

Steps to reproduce

Install feeds_ex. Load a feed where the JSON parser fails to parse. e.g. comma in numbers, or blank array.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request

Status

Needs work

Version

1.0

Component

Code

Created by

🇦🇺Australia interlated

Live updates comments and jobs are added and updated live.

Incomplete comments

Sign in to follow issues

Merge Requests

!43Make it easier to determine which feed resulted in invalid JSON
Open
🇯🇵Japan ptmkenny
updated about 1 year ago

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 year ago →
🇯🇵Japan ptmkenny
Merge request !43log which feed has invalid JSON → (Open) created by ptmkenny
Open in Jenkins → Open on Drupal.org →
Core: 9.5.5 + Environment: PHP 7.4 & MySQL 5.7
last update about 1 year ago
105 pass, 2 fail
Status changed to Needs work about 1 year ago2:34pm 22 April 2024
Comment about 1 year ago →
🇯🇵Japan ptmkenny
This should be extended to handle JsonPathParser too, not just JmesPathParser.
Pipeline finished with Failed
about 1 year ago
Total: 412s
#153429
Comment about 1 year ago →
🇳🇱Netherlands megachriz
This should use dependency injection. And after that, the failing test should be updated to use a mock of that dependency.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024