-
Notifications
You must be signed in to change notification settings - Fork 20
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
Very nice lib! But a few things to add #3
Comments
👍 |
@burzum All great suggestions, thanks for the feedback.
|
- Adds Flux to the Sortiz\Tools namespace - Implements PSR-2 Compliance (Tabs over Spaces) - Updates version number on Flux and this readme file - Updates the class instantiation with fully qualified class name on example.php - Adds references to other repos that have ported flux - Addresses concerns outlined in [Issue #3](#3)
@selvinortiz cool, anything that you want help let me know, really great project! |
composer is a must for any PHP library ! Let's hope it comes quickly ;-) |
@selvinortiz 👍 Thanks for the fast response. |
~- Fixes internal namespace conflict - Changes namespace from Sortiz\Tools to SelvinOrtiz\Utils\Flux - Adds composer support [Issue #3](#3) - Adds the addSeed() and removeSeed() methods [Issue #4](#4) - Adds the getInstance() static method - Adds FluxUrlExample.php, FluxDateExample.php, and FluxPhoneExample.php - Adds getSeed() to get the seed without forcing __toString on the object - Adds getSegment() to extract a segment (capturing group) from the pattern - Implements unit tests (60% coverage) [Issue #3](#3) - Implements Full PSR-2 Compliance (Tabs over Spaces) - Enables the seed on match() and replace() [Issue #4](#4) - Removes example.php and defines them elsewhere - Moves examples into /etc and defines one example per file - Other small fixes and additions
I've got unit tests in place (60% coverage), namespace, PSR-2 compliance (tabs over spaces), and composer support. I'll be uploading to packagist.org some time today and update the readme when it's done. Thank you all for your feedback and support! |
@krolow Thank you. I'll try to find some time to add contributing notes and a |
👍 |
I'd noticed that you have some system to create tags but the repository doesn't have tags (releases) itself. I'll suggest making use of Semantic Version. By the way it will be important to Composer. |
Just another 👍 for the good work :) |
Thanks @burzum : ) Great point @moacirosa and yes, tagged releases are definitely important for composer... This weekend project of mine has gotten more interest than I had anticipated so I'm sorry for not getting everything setup properly right out of the gate but my goal is to ultimately make the library usable, standards compliant, environment friendly, and robust. I work in an enterprise, team environment so I know this things are important and I'll treat them as such. Again, thanks for all your feedback and support! |
@moacirosa Tagged releases have been enabled https://github.com/selvinortiz/flux/releases and will be used from now on using Semantic Version as suggested by you and good practices in general. |
💯 Man... Its awesome! 3 days and all this progress. Thanks for accepting the sugestion and I'll try to help in some way at night (UTC-3) |
@moacirosa Thanks bro, I appreciate that! |
Except this it's a great lib!
The text was updated successfully, but these errors were encountered: