-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Getters for underlying libraries and setters for data fields #17
Conversation
…are/specifikace-formatu/); Basic data sanitation; Getter for Spayd; Getter for underlying QR code builder
Thanks for contribution, I will look at it soon. :) |
How much of a rush are you in? It's going to need unit tests at the very least, and looking at the whole thing, I'd probably refactor it. If you are in a hurry I'd release it when the tests are added, if you're not in a hurry I'll refactor it first. |
I could add some tests. What would you refactor? Please don't break my code :) |
I did just small refactoring for current version, but I'm working on big refactor which I will release as major update. Add test for the |
I moved the sanitation to new utility class to test it easily and make main class cleaner. |
Also I would suggest to improve the sanitation by transliterating non ISO-8859-1 symbols and striping special characters. private function sanitize(string $value)
{
return \voku\helper\UTF8::to_filename(mb_strtoupper(\voku\helper\UTF8::to_ascii($value), 'UTF-8'), false, ' ');
} Not sure you if you like additional dependencies in your project. |
I created a new branch for v3, so if you wish, you can add it there. I will release it as next v3 release (if it will be backward compatible) and refactor it to v4 (if it will make sense). |
|
Note me here when it will be ready and I will look at it once again and merge it. :) |
I think let's leave the improved sanitation to v4. Adding additional library could cause version conflicts for someone. |
So is this ready to review/merge? :) BTW I don't think that changing requirements is an issue - these who will have conflict will be able to install previous version (and also following version in this case). |
I think you can merge. I don't have time before next week to deal with this.
…On Sat, Jun 1, 2024, 13:28 Petr Knap ***@***.***> wrote:
So is this ready to review/merge? :)
BTW I don't think that changing requirements is an issue - these who will
have conflict will be able to install previous version (and also following
version in this case).
—
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABPY2DSUEJV3BAIEE5VPYDZFGO6RAVCNFSM6AAAAABIBT6HSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGM4TOMZWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Constants and setters for data fields based on specification https://qr-platba.cz/pro-vyvojare/specifikace-formatu/.
Basic data sanitation.
Getters for underlying Spayd and QR code builder to be able to modify certain elements.