Upgrade target framework to resolve package compatibility issues (resolves #42) #98
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #42
…ility - Updated TargetFramework from net6 to net8.0 to resolve compatibility issues - Added Platform.Data.Doublets package reference with compatible version 0.17.2 - This resolves the NU1202 error where Platform.Data.Doublets.Sequences 0.5.2 requires net7.0 or higher target framework Addresses issue #42: The original request was to upgrade from netcoreapp3.0 to netcoreapp3.1, but the project has evolved and now needs a modern target framework to work with current dependencies. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
konard
changed the title
Member
Author
|
🤖 AI Work Session Started Starting automated work session at 2026-01-12T20:42:57.408Z The PR has been converted to draft mode while work is in progress. This comment marks the beginning of an AI work session. Please wait working session to finish, and provide your feedback. |
Updated code to work with Platform.Data.Doublets v0.18.1 and Platform.Data.Doublets.Sequences v0.6.5: - Updated namespaces: moved Unicode, Time, Numbers.Raw to Sequences package - Changed Memory.Split.Specific to Memory.Split.Generic - Replaced UInt32SplitMemoryLinks with generic SplitMemoryLinks<TLinkAddress> - Removed UInt32Links decorator (no longer needed) - Added unicodeSequenceMarker parameter to UnicodeSequenceToStringConverter - Added CriterionMatchers namespace for TargetMatcher Build now succeeds with only warnings (no errors). Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Member
Author
✅ Work Session CompletedSuccessfully fixed all compilation errors and API compatibility issues. The code now builds successfully with the latest Platform.Data.Doublets packages. What was fixed:
Test Results:
The PR is now ready for review and merge. All requirements from issue #42 have been completed. |
Member
Author
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
Now working session is ended, feel free to review and add any feedback on the solution draft. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses issue #42 by upgrading the target framework and fixing API compatibility issues with the latest Platform.Data.Doublets packages.
Changes:
net6tonet8.0Background
Issue #42 originally requested upgrading from
netcoreapp3.0tonetcoreapp3.1, but the project has since evolved through multiple framework upgrades (netcoreapp3.0→net5→net6→net8.0). The main challenge was updating the code to work with breaking changes in the Platform.Data.Doublets API between versions.API Changes Fixed
Updated code to work with the latest Platform.Data.Doublets packages:
Namespace migrations:
Platform.Data.Doublets.Unicode→Platform.Data.Doublets.Sequences.UnicodePlatform.Data.Doublets.Time→Platform.Data.Doublets.Sequences.TimePlatform.Data.Doublets.Numbers.Raw→ remains in core packagePlatform.Data.Doublets.Sequences.Numbers.Rawfor number convertersPlatform.Data.Doublets.Memory.Split.Specific→Platform.Data.Doublets.Memory.Split.GenericType updates:
UInt32SplitMemoryLinkswith genericSplitMemoryLinks<TLinkAddress>UInt32Linksdecorator (no longer needed in new API)CriterionMatchersnamespace forTargetMatcherConstructor signature changes:
unicodeSequenceMarkerparameter toUnicodeSequenceToStringConverterTest Results
Warnings (non-blocking)
The build produces some warnings related to nullable reference types and obsolete BenchmarkDotNet methods. These are pre-existing issues and don't affect functionality.
🤖 Generated with Claude Code
Resolves #42