You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2021. It is now read-only.
Using e.g. {{MessagePort/postMessage()}} is reported as ambiguous when used in ReSpec, despite this being a well-defined single definition.
I think because xref provides both an argument-full and an argument-less version of the method, it appears duplicated in search results, and thus raises an error when used in ReSpec.
xref should de-duplicate methods in that situation.
The text was updated successfully, but these errors were encountered:
xref should de-duplicate methods in that situation.
What should be the correct de-duplication behavior in case of {{MessagePort/postMessage()}}? We've postMessage(message, transfer), postMessage(message, options) converting into postMessage(). The present solution is to be explicit. Should we remove postMessage() and keep only explicit versions?
Using e.g.
{{MessagePort/postMessage()}}
is reported as ambiguous when used in ReSpec, despite this being a well-defined single definition.I think because xref provides both an argument-full and an argument-less version of the method, it appears duplicated in search results, and thus raises an error when used in ReSpec.
xref should de-duplicate methods in that situation.
The text was updated successfully, but these errors were encountered: