Use new write handlers style in the example #38
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 updates the CRUD example to use the new write handlers API style as requested in issue #36.
Key Changes
links.Create()tolinks.CreatePoint()extension method, which internally useslinks.Create(substitution: null, handler: null)links.Update(link, newSource: link, newTarget: link)to the new API pattern using restriction and substitution parameters:links.Update(restriction: restriction, substitution: substitution, handler: null)New Write Handlers API Pattern
The new API follows this pattern:
Create(IList<TLinkAddress>? substitution, WriteHandler<TLinkAddress>? handler)Update(IList<TLinkAddress>? restriction, IList<TLinkAddress>? substitution, WriteHandler<TLinkAddress>? handler)Delete(IList<TLinkAddress>? restriction, WriteHandler<TLinkAddress>? handler)Test Results
✅ The application builds successfully
✅ The application runs without errors and produces expected output
✅ Demonstrates both the convenient extension method (
CreatePoint()) and the direct new API usage patternsTest plan
dotnet builddotnet runFixes #36
🤖 Generated with Claude Code