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

fix: ensure counter strictness #52

Merged

Conversation

kekavc24
Copy link
Owner

Description

  • Fixes issue where the counter used by the Finder leaked matches as long as other matches within the enclosing class had not exceeded the limit.

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

> make MatchedNodeData a mutable standalone class
> override increment method in counter to only add values below limit
> try updating counter before yielding matches. Let counter decide the validity of the match after matching it.
> call internal node member as MatchedNode is no longer a subclass of NodeData
@kekavc24 kekavc24 added the fixes bug Pull request fixes bug with pending release to production label Mar 15, 2024
@kekavc24 kekavc24 merged commit 808a482 into fix/allow-for-dynamic-indexing Mar 15, 2024
2 of 3 checks passed
@kekavc24 kekavc24 deleted the fix/ensure-counter-strictness branch March 15, 2024 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixes bug Pull request fixes bug with pending release to production
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant