Conversation
Feature file, interview notes, DoD in product_definition.md, and test stubs for removing ~= (APPROXIMATELY_EQUAL) operator.
Squash-merge feature/remove-fuzzy-match-operator. Removes the ~= fuzzy match operator from condition evaluation, updates loader to reject unknown operators, and migrates loader behavior tests to unit tests.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
~=(APPROXIMATELY_EQUAL) fuzzy match operator from specification, implementation, and documentation. The operator is now a parse error (FlowParseError) with exactly 6 valid operators:==,!=,>=,<=,>,<.1.0.0, changelog entry, README rewritten with PyPI badges and installation instructions.docs/index.html): comprehensive role-based layout with syntax reference, operator tables, and examples.Changes
Feature: Remove fuzzy match operator
APPROXIMATELY_EQUALfromConditionOperatorenum (flowr/domain/condition.py)~=detection in loader with clearFlowParseError(flowr/domain/loader.py)tests/features/remove_fuzzy_match_operator/and unit tests intests/unit/loader_test.pytests/features/condition_operators_test.py,tests/unit/condition_test.py)Specification updates
docs/spec/flow_definition_spec.md: lists exactly 6 operatorsdocs/spec/glossary.md: operator table updated, "Fuzzy Match" entry retireddocs/spec/product_definition.md: removed fuzzy match referencesdocs/spec/system.md: updated condition operator referencesADR deprecation
docs/adr/ADR_20260426_fuzzy_match_algorithm.md: deprecation notice addeddocs/adr/ADR_20260426_condition_inlining.md: cross-reference updatedRelease artifacts
pyproject.toml: version bumped to 1.0.0CHANGELOG.md: v1.0.0 entryREADME.md: rewritten with clear purpose, audience, PyPI badgesdocs/index.html: comprehensive spec reference pagedocs/branding/branding.md: updated assetsdocs/assets/logo.svg,docs/assets/banner.svg: refreshedTraceability
tests/features/remove_fuzzy_match_operator/condition_removal_test.pytests/features/remove_fuzzy_match_operator/condition_removal_test.pyCommits (3)
4b79eca— chore: baseline remove-fuzzy-match-operator planning artifactsdd0665b— feat(condition): remove ~= fuzzy match operatord257e87— release: v1.0.0 First Stone