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

[CoreData] Move CoreData into the .NET age. #13718

Merged
merged 1 commit into from
Jan 14, 2022

Conversation

rolfbjarne
Copy link
Member

  • Remove obsolete API from .NET.
  • Change API marked with XAMCORE_4_0 due to naming problems to be in .NET.
  • Change API marked with XAMCORE_4_0 due to using non-generic NSDictionary to be
    in XAMCORE_5_0 instead (yay!). This is because of All empty NSDictionary instances have the same underlying native handle #13704, which can make using
    generic NSDictionary in API buggy, and I feel it's a bit too risky to change this
    for .NET with the time we have available (no time to fix All empty NSDictionary instances have the same underlying native handle #13704). Additionally,
    moving this to XAMCORE_5_0 makes it possible to keep grepping for XAMCORE_4_0 to
    see what's left. Update all the CoreData API to be better as defined by our XAMCORE_4_0
    define. Mostly using generic NSSet/NSDictionary types instead of the non-generic
    ones, and other misc naming improvements.
  • Change API marked with XAMCORE_4_0 due to both of the above to do both of the
    above - add a version of the naming issue fixed for .NET + a version with the generic
    dictionary for XAMCORE_5_0.

* Remove obsolete API from .NET.
* Change API marked with XAMCORE_4_0 due to naming problems to be in .NET.
* Change API marked with XAMCORE_4_0 due to using non-generic NSDictionary to be
  in XAMCORE_5_0 instead (yay!). This is because of xamarin#13704, which can make using
  generic NSDictionary in API buggy, and I feel it's a bit too risky to change this
  for .NET with the time we have available (no time to fix xamarin#13704). Additionally,
  moving this to XAMCORE_5_0 makes it possible to keep grepping for XAMCORE_4_0 to
  see what's left. Update all the CoreData API to be better as defined by our XAMCORE_4_0
  define. Mostly using generic NSSet/NSDictionary types instead of the non-generic
  ones, and other misc naming improvements.
* Change API marked with XAMCORE_4_0 due to both of the above to do both of the
  above - add a version of the naming issue fixed for .NET + a version with the generic
  dictionary for XAMCORE_5_0.
@rolfbjarne rolfbjarne added not-notes-worthy Ignore for release notes run-dotnet-tests Run all the .NET tests breaking-change If an issue or a pull request represents a breaking change labels Jan 13, 2022
@vs-mobiletools-engineering-service2
Copy link
Collaborator

❌ [PR Build] Tests failed on Build ❌

Tests failed on Build.

API diff

✅ API Diff from stable

View API diff
View dotnet API diff
View dotnet legacy API diff
View dotnet iOS-MacCatalayst API diff

API Current PR diff

ℹ️ API Diff (from PR only) (please review changes)

View API diff
View dotnet API diff
View dotnet legacy API diff
View dotnet iOS-MacCatalayst API diff

Generator diff

ℹ️ Generator Diff (please review changes)

GitHub pages

Results can be found in the following github pages (it might take some time to publish):

Test results

3 tests failed, 145 tests passed.

Failed tests

  • monotouch-test/Mac [dotnet]/Debug [dotnet]: Failed (Test run failed.
    Tests run: 2571 Passed: 2411 Inconclusive: 6 Failed: 1 Ignored: 159)
  • monotouch-test/Mac [dotnet]/Debug (static registrar) [dotnet]: Failed (Test run failed.
    Tests run: 2568 Passed: 2409 Inconclusive: 6 Failed: 1 Ignored: 158)
  • xammac tests/Mac Modern/Release: TimedOut (Execution timed out after 1200 seconds.
    Test run crashed)

Pipeline on Agent XAMBOT-1106.BigSur'
Merge b1ed56b into 76cd53f

@rolfbjarne
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@vs-mobiletools-engineering-service2
Copy link
Collaborator

❌ [PR Build] Tests failed on Build ❌

Tests failed on Build.

API diff

✅ API Diff from stable

View API diff
View dotnet API diff
View dotnet legacy API diff
View dotnet iOS-MacCatalayst API diff

API Current PR diff

ℹ️ API Diff (from PR only) (please review changes)

View API diff
View dotnet API diff
View dotnet legacy API diff
View dotnet iOS-MacCatalayst API diff

Generator diff

ℹ️ Generator Diff (please review changes)

GitHub pages

Results can be found in the following github pages (it might take some time to publish):

Test results

3 tests failed, 145 tests passed.

Failed tests

  • monotouch-test/Mac [dotnet]/Debug [dotnet]: Failed (Test run failed.
    Tests run: 2622 Passed: 2462 Inconclusive: 6 Failed: 1 Ignored: 159)
  • monotouch-test/Mac [dotnet]/Debug (static registrar) [dotnet]: Failed (Test run failed.
    Tests run: 2619 Passed: 2459 Inconclusive: 6 Failed: 2 Ignored: 158)
  • fsharp/Mac Catalyst [dotnet]/Debug [dotnet]: TimedOut (Execution timed out after 1200 seconds.
    No test log file was produced)

Pipeline on Agent XAMBOT-1100.BigSur'
Merge b1ed56b into 9894605

@rolfbjarne
Copy link
Member Author

Test failures are unrelated:

@rolfbjarne rolfbjarne merged commit e963fc6 into xamarin:main Jan 14, 2022
@rolfbjarne rolfbjarne deleted the dotnet-coredata-xamcore4-take2 branch January 14, 2022 16:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change If an issue or a pull request represents a breaking change not-notes-worthy Ignore for release notes run-dotnet-tests Run all the .NET tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

All empty NSDictionary instances have the same underlying native handle
6 participants