Skip to content

Code cleanup and PSR-2 compatibility #29

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

Merged
merged 2 commits into from
Jan 4, 2020

Conversation

RSpeekenbrink
Copy link
Contributor

Cleanup the code to comply with the more modern best practices.

And a small request to add a 0.3.0 tag or release 1.0.0 since its bad to use an adoption of the master branch 😅

Cleanup the code and follow PSR-2 guidelines
update readme with markdown codeblock syntax and typehinting aswell as making it non Laravel 5 specific.
@barryvdh barryvdh merged commit e6bfc4c into barryvdh:master Jan 4, 2020
@barryvdh
Copy link
Owner

barryvdh commented Jan 4, 2020

This doesn't change functionality right3? So why is a tag needed?

@RSpeekenbrink
Copy link
Contributor Author

No it doesn't change functionality but the readme sugests installing v0.3.0. This tag does not exist yet and thereby it installs dev-master since the branch is defined as 0.3-dev in the composer json. If there are changes in functionality to be made in the master branch this can cause conflicts on production environments using the suggested 0.3.* version.

@RSpeekenbrink
Copy link
Contributor Author

I just saw that the latest functionality changes are tagged as 0.2.1. Maybe make that the suggested version in the readme or remove versioning from the require command in the readme in total?

@barryvdh
Copy link
Owner

barryvdh commented Jan 4, 2020

Yeah we should just remove the version there

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