Make bikeshed complain less #162

Activity

1. miketaylr commented on Oct 18, 2021

   

   miketaylr

   on Oct 18, 2021

   ContributorAuthor

   More actions

   whatwg/fetch@efde35d is responsible for LINE ~297: No 'dfn' refs found for 'transmitted bytes'.

   whatwg/fetch@7e5c922 is responsible for LINE ~296: No 'dfn' refs found for 'process request body'.
2. miketaylr commented on Oct 18, 2021

   

   miketaylr

   on Oct 18, 2021

   Last edited by miketaylr

   ContributorAuthor

   More actions

   whatwg/fetch@12dd6fa#diff-b4827ee42aceaf9dc3e7216f72262d81c32217e9996fb70a657f259e3ac92604L168 created LINK ERROR: No 'dfn' refs found for 'process response' that are marked for export.
3. miketaylr commented on Oct 18, 2021

   

   miketaylr

   on Oct 18, 2021

   ContributorAuthor

   More actions

   I'm not really sure what caused LINE ~701: No 'dfn' refs found for 'wait' that are marked for export.. I ran out of energy. :(
4. miketaylr

   added 2 commits that reference this issue on Oct 18, 2021

   Fix a big pile of linking errors.

   ...

   6aa42be

   Fix a big pile of linking errors.

   ...

   09e8c80
5. miketaylr commented on Oct 18, 2021

   

   miketaylr

   on Oct 18, 2021

   ContributorAuthor

   More actions

   Whenever whatwg/xhr#333 lands/settles, 'process request body' can be fixed (probably?)
6. annevk commented on Oct 19, 2021

   

   annevk

   on Oct 19, 2021

   More actions

   Note that for "process request body" while you can fix the xref issue, a more substantial rewrite is needed to align with the new fetch calling conventions.

   I recently wrote https://fetch.spec.whatwg.org/#fetch-elsewhere to elaborate a bit on that, though it could be more useful still as that doesn't have examples.

   👍React with 👍1Reacted by Mike Taylor