Skip to content

Attempts to deserialize payload from the coverage endpoint#287

Open
xcambar wants to merge 1 commit intoember-cli-code-coverage:masterfrom
xcambar:attempt_deserialize_json
Open

Attempts to deserialize payload from the coverage endpoint#287
xcambar wants to merge 1 commit intoember-cli-code-coverage:masterfrom
xcambar:attempt_deserialize_json

Conversation

@xcambar
Copy link

@xcambar xcambar commented Sep 9, 2020

fixes #286

As discussed in #286, this PR restores the initial behavior that attempts to deserialize a stringified JSON.

@RobbieTheWagner RobbieTheWagner changed the title Attemps to deserialize payload from the coverage endpoint Attempts to deserialize payload from the coverage endpoint Sep 15, 2020
return;
}

if (typeof data === 'string') {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I still want to understand why data would be a string. 🤔

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@xcambar - Have you looked into this?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not thoroughly, but an initial look did not exclude that the behavior originates in istanbul-lib-coverage, unfortunately.

@rwjblue
Copy link
Collaborator

rwjblue commented Sep 21, 2020

Needs a rebase now that #289 has landed...

@xcambar xcambar force-pushed the attempt_deserialize_json branch from e4d16d9 to ddc8536 Compare September 22, 2020 13:46
@xcambar
Copy link
Author

xcambar commented Sep 22, 2020

rebased

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

middleware still returns a string, when JSON is expected

2 participants