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

Splink 4 blocking rule/blocking rule creator fixes #2103

Merged
merged 9 commits into from
Mar 28, 2024

Conversation

RobinL
Copy link
Member

@RobinL RobinL commented Mar 27, 2024

There are a variety of linker functions that take blocking rules as an argument directly (i.e. not as part of the settings object) e.g. count_num_comparisons_from_blocking_rule

This PR ensures these functions accept a BlockingRuleCreator (i.e. from block_on), and do not accept a BlockingRule (which is now internal and shouldn't be used by end users)

I created a new file blocking_rule_creator_utils.py primarily because of problems with circular imports.

I found many of these problems when doing the example/tutorials notebooks and left TODOs to fix. There's no need to check the modifications to them, as I'm just reverting the code in them to what it should have been in the first place

@RobinL RobinL changed the title Blocking rule fixes (WIP) Splink 4 blocking rule/blocking rule creator fixes Mar 27, 2024
@RobinL RobinL changed the title (WIP) Splink 4 blocking rule/blocking rule creator fixes Splink 4 blocking rule/blocking rule creator fixes Mar 27, 2024
@RobinL RobinL requested a review from ADBond March 27, 2024 16:16
Copy link
Contributor

@ADBond ADBond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! 👍

@RobinL RobinL merged commit 6d60b53 into splink4_dev Mar 28, 2024
22 checks passed
@RobinL RobinL deleted the blocking_rule_fixes branch March 28, 2024 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants