Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

consider providing a json serializer for Request and Response #22

Closed
wanderview opened this issue Mar 3, 2015 · 3 comments
Closed

consider providing a json serializer for Request and Response #22

wanderview opened this issue Mar 3, 2015 · 3 comments

Comments

@wanderview
Copy link
Member

Currently JSON.stringify() returns simply {} for Request and Response objects. It might be nice to define serializers for these classes to help developers debug their code.

http://heycam.github.io/webidl/#idl-serializers
@annevk
Copy link
Member

annevk commented Mar 4, 2015

So there are a bunch of objects without pretty JSON representations. Shouldn't developer tools have a way to look at all of them nicely? Or do you want to serialize these and transmit them to the server or some such?

@wanderview
Copy link
Member Author

Yea, this is mainly for devtools and console.log. I'm fine either way. Just wanted to note that I had someone testing the API get tripped up by this.

@annevk
Copy link
Member

annevk commented Mar 27, 2015

Let's revisit once there's an actual use case.

@annevk annevk closed this as completed Mar 27, 2015
yutakahirano added a commit that referenced this issue Jun 23, 2020
@yutakahirano
# This is a combination of 2 commits.
db9fbcd 
# This is the 1st commit message:

# This is a combination of 23 commits.
# This is the 1st commit message:

Integrate CORP and COEP

This is part of the introduction of COEP
(whatwg/html#5454). The CORP check now takes
COEP into account. Also, responses coming from service workers
are checked.

# This is the commit message #2:

Update fetch.bs

Co-authored-by: Domenic Denicola <d@domenic.me>
# This is the commit message #3:

Update fetch.bs

Co-authored-by: Domenic Denicola <d@domenic.me>
# This is the commit message #4:

fix

# This is the commit message #5:

fix

# This is the commit message #6:

fix

# This is the commit message #7:

fix

# This is the commit message #8:

fix

# This is the commit message #9:

fix

# This is the commit message #10:

fix

# This is the commit message #11:

fix

# This is the commit message #12:

fix

# This is the commit message #13:

fix

# This is the commit message #14:

fix

# This is the commit message #15:

fix

# This is the commit message #16:

fix

# This is the commit message #17:

fix

# This is the commit message #18:

Update fetch.bs

Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
# This is the commit message #19:

Update fetch.bs

Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
# This is the commit message #20:

fix

# This is the commit message #21:

fix

# This is the commit message #22:

fix

# This is the commit message #23:

fix

# This is the commit message #2:

fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wanderview @annevk