Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Able to get collection of all objects in table #25

Closed
AndyDentFree opened this issue Jul 20, 2015 · 1 comment
Closed

Able to get collection of all objects in table #25

AndyDentFree opened this issue Jul 20, 2015 · 1 comment
Assignees

Comments

@AndyDentFree
Copy link
Contributor

As a test that our collections are working properly, Andy thinks this should allow using Linq to Objects to query the collection, which is woeful but useful for testing

@AndyDentFree AndyDentFree added this to the Phase 1 milestone Jul 20, 2015
@AndyDentFree AndyDentFree added ready and removed ready labels Jul 22, 2015
@AndyDentFree AndyDentFree self-assigned this Jul 23, 2015
AndyDentFree added a commit that referenced this issue Jul 27, 2015
RealmWinOnly.sln
- add DebugMock configuration

Realm.sln
- added DebugMock configuration for all as copy of Debug

CoreProvider.cs
- copied to common CoreProvider.shared.cs

Interop.Win32.csproj
Interop.XamrainAndroid.csproj
Interop.XamarinIOS.csproj
Interop.XamarinMac.csproj
- linked in CoreProviderFactory.shared.cs
- removed its own CoreProvider.cs
- linked in CoreProvider.shared.cs

RealmNet.Tests.csproj
- linked in CoreProviderFactory.shared.cs
- added DebugMock configuration for AnyCPU defining MOCKING_CONFIG
- discard TestHelpers\CoreProviderStub.cs (temporarily)

CoreProviderFactory.shared.cs
- added file

WeaverTests.cs
- removed using clause for Tests.TestHelpers
- remove coreProviderStub_ to use ProviderFactory instead
- commented out asserts checking the coreProvierStub because mock will be evaluated differently

QueryTests.cs
- comment out for now as expects queryProviderStub to implement different interface
@AndyDentFree
Copy link
Contributor Author

Due to waffle smarts and getting an issue number wrong in a branch, this has been merged into #28 because that's where the code went

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant