reactiveui / Akavache

An asynchronous, persistent key-value store created for writing desktop and mobile applications, based on SQLite3. Akavache is great for both storing important data as well as cached local data that expires.

Home Page:https://evolve.xamarin.com/session/56e2044afd00c0253cae33a3

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG] Akavache.Drawing Registrations uses same namespace as Akavache.Core

gtbuchanan opened this issue · comments

Describe the bug
The Registrations class in the Akavache.Drawing package uses the namespace Akavache, which conflicts with the Registrations class in the main Akavache package.

Steps To Reproduce
Reference Akavache and Akavache.Drawing and attempt to call Registrations.Start

Expected behavior
Registrations in Akavache.Drawing should probably be in the Akavache.Drawing namespace to avoid the conflict. BitmapImageMixin should probably be there as well.

Additional context
I encountered this while attempting to upgrade from Akavache 6.5.1.

My current workaround is to use an extern alias in the csproj but this is obviously not ideal:

<Target Name="AkavacheDrawingAlias" BeforeTargets="FindReferenceAssembliesForReferences;ResolveReferences">
  <ItemGroup>
    <ReferencePath Condition="'%(FileName)' == 'Akavache.Drawing'">
      <Aliases>AkavacheDrawing</Aliases>
    </ReferencePath>
  </ItemGroup>
</Target>

Workaround Usage:

extern alias AkavacheDrawing;
...
.SelectMany(AkavacheDrawing::Akavache.BitmapImageMixin.ThrowOnBadImageBuffer);

Hey @gtbuchanan 👋,

Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider contributing financially.

https://opencollective.com/reactiveui

PS.: We offer priority support for all financial contributors. Don't forget to add priority label once you start contributing 😄

An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms!

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.