- From: Sam Gammon <notifications@github.com>
- Date: Mon, 23 Jan 2023 15:45:27 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/issues/1575/1401158918@github.com>
@domfarolino I see. thank you for the references, I'll take a look. What about a custom `[Symbol.*]` which provides a function tailored to emit a better console representation? I understand stringification is already a point of API compatibility, so surely an opt-in upgrade for implementers would be best if this is fixed by spec. > Feel free to file a bug on Console for this, but I will say that standard doesn't get a whole lot of love these days so any large contributions are more likely to materialize with help from the community! Forgive me, I'm new to standards contribution :) I would love to file a contribution for this if it is a welcome PR from WhatWG's perspective. How do I get started? I'll take a look at that spec, contribution guides, etc. Would I just fork, and file a PR change to the spec itself? I happen to be _implementing_ the Fetch API in a [different project entirely](https://alpha.elide.dev/) which involves a JS runtime, so I have an opportunity to dogfood those new Console extensions myself and iterate quickly if that is at all helpful. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1575#issuecomment-1401158918 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1575/1401158918@github.com>
Received on Monday, 23 January 2023 23:45:40 UTC