Lentil Hoffman
d7c4fda93e
Core Changes: - Completely rewrote CustomResolver reducer with dependency-ordered processing - Enhanced plugin initialization with proper dependency injection - Improved delta processing and property value tracking - Added robust error handling for duplicate property IDs Resolver Improvements: - Updated to use new accumulator structure - Implemented execution order processing for plugins - Enhanced debug logging and error reporting - Simplified TimestampResolver by removing unused initializer Configuration Updates: - Added TypeScript path aliases for test helpers - Improved module resolution paths Key Benefits: - More robust plugin dependency management - More efficient state updates - Enhanced type safety - Better error messages and debugging - More consistent plugin initialization This refactoring focuses on improving the robustness of the resolver, especially around plugin lifecycle management and dependency handling. The changes ensure better separation of concerns and more predictable behavior when dealing with complex plugin dependencies.
14 lines
627 B
Markdown
14 lines
627 B
Markdown
# Test structure
|
|
- before test, initialize node and lossless view
|
|
- when test begins, create and ingest a series of deltas
|
|
- instantiate a resolver, in this case using custom resolver plugins
|
|
- call the resolver's initializer with the view
|
|
- call the resolver's reducer with the view
|
|
- call the resolver's resolver with the view
|
|
- expect the resolver to return the expected result
|
|
|
|
# Follow-up
|
|
- why isn't the resolver being called automatically, by event dispatch?
|
|
- we can prepare an array of deltas and pass it to a test helper,
|
|
- So our entire test case should consist of the deltas, the resolver, and the expected result.
|