Fix: Model loader callback consistency #31
Merged
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.
Resolves #29
Problem
The two model loaders had inconsistent behavior when watching for changes:
This inconsistency blocks a proper solution for #30 (webhook notifications on model changes).
Changes
Base ModelLoader Class
lastHashproperty for change trackinggetModelsHash(models)method for consistent hash calculation across all loadersN8nApiModelLoader
getModelsHash()from base class instead of firing callback on every polllastModelsHashtolastHashfor consistencyJsonFileModelLoader
getModelsHash()from base classgetFileHash()method (no longer needed)Tests
lastHashinstead oflastModelsHashBenefits
Testing
All 367 tests pass with 95.82% code coverage.