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

[MRG] Refactor method Table.set_edges for readability #371

Closed

Conversation

tomprogrammer
Copy link
Contributor

From all close points stored in i, j or k only the first one was used therefore the new function find_close_point only returns the first match if any.

Similar code is hoisted out of loops and branches and the while loops are more clearly expressed with for loops.

This is an alternative approach to #328, that leads to even better structured code in my opinion.

From all close points stored in `i`, `j` or `k` only the first one was used
therefore the new function `find_close_point` only returns the first match if
any.

Similar code is hoisted out of loops and branches and the `while` loops
are more clearly expressed with `for` loops.
@tomprogrammer tomprogrammer changed the title Refactor method Table.set_edges for readability [MRG] Refactor method Table.set_edges for readability May 17, 2023
@MartinThoma
Copy link
Collaborator

Hey!

As camelot is dead, we try to build a maintained fork at pypdf_table_extraction.

Do you want to open the PR against that branch so that we can merge your improvement?

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