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
In our codebase we have a protocol called Matchable. This clashes with the Matchable protocol defined in the Mockable package. I think a safe precaution would be to use a fully qualified identifier in the code generated by the macro.
Unfortunately this will require some renaming, since Mockable will resolve to the Mockable protocol instead of the package.
Perhaps this can be extended to other protocols such as CaseIdentifiable, EffectBuilder and AssertionBuilder as well.
The text was updated successfully, but these errors were encountered:
wvteijlingen-npo
changed the title
Mockable.Matchable protocol clashes with our own protocol from code baseMatchable protocol clashes with protocol from our own code base
Sep 5, 2024
wvteijlingen-npo
changed the title
Matchable protocol clashes with protocol from our own code base
Use fully qualified identifiers in macro generated code
Sep 6, 2024
Uh oh!
There was an error while loading. Please reload this page.
In our codebase we have a protocol called
Matchable
. This clashes with theMatchable
protocol defined in the Mockable package. I think a safe precaution would be to use a fully qualified identifier in the code generated by the macro.Unfortunately this will require some renaming, since
Mockable
will resolve to theMockable
protocol instead of the package.Perhaps this can be extended to other protocols such as
CaseIdentifiable
,EffectBuilder
andAssertionBuilder
as well.The text was updated successfully, but these errors were encountered: