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

Support padding in renderImg #51

Merged
merged 2 commits into from
Jan 29, 2024
Merged

Support padding in renderImg #51

merged 2 commits into from
Jan 29, 2024

Conversation

mariusandra
Copy link
Contributor

@mariusandra mariusandra commented Jan 28, 2024

When adding QR code support to my own project, I had to tweak renderImg to support customizable amounts of padding around the code.

@mariusandra mariusandra changed the title Support padding in renderImg Support padding in renderImg Jan 28, 2024
@aruZeta aruZeta changed the base branch from main to develop January 28, 2024 20:19
Copy link
Owner

@aruZeta aruZeta left a comment

Choose a reason for hiding this comment

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

Hey! Thanks for the PR, it lgtm but I left a minor comment with a minor improvement. After you change that little thing I will merge to develop and release 3.1.0 :)

Comment on lines 50 to 52
padding: uint8 = 5,
img: Image = Image(width: 0, height: 0),
imgCoords: tuple[x, y, w, h: uint8] = self.genDefaultCoords
Copy link
Owner

Choose a reason for hiding this comment

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

I think it would be better if you made the new parameter the last one, so that backwards compatibility remains, although I actually like it more were you left it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That makes sense, moved it to the end.

@aruZeta
Copy link
Owner

aruZeta commented Jan 28, 2024

Seems like I have to fix the GH actions haha (what did I expect after ~1.5y), I hope you can wait a bit, I will try to work on it tomorrow.

@mariusandra
Copy link
Contributor Author

Cool, thanks for taking it on so quickly. The workaround known as "copy paste" does the job for now 😅, so no there's rush from my side.

@aruZeta
Copy link
Owner

aruZeta commented Jan 29, 2024

Seems like it was just the version of the GH actions, I'm merging this directly to avoid the hassle of getting you to merge my develop onto your branch.

@aruZeta aruZeta merged commit 8cd8f82 into aruZeta:develop Jan 29, 2024
0 of 2 checks passed
@aruZeta aruZeta mentioned this pull request Jan 29, 2024
@aruZeta
Copy link
Owner

aruZeta commented Jan 29, 2024

Release 3.1.0 with this PR has been released! Although I no longer maintain this repo, PRs are always welcome :)

@mariusandra
Copy link
Contributor Author

Thanks again! I updated my deps and could now remove the copy pasta. Also 🙌 for keeping up the maintenance work!

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