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

Docs improvement #29

Merged
merged 1 commit into from
Dec 27, 2016
Merged

Docs improvement #29

merged 1 commit into from
Dec 27, 2016

Conversation

lukasoppermann
Copy link

I think this could make it easier to understand. I would also add an example to clarify what the xss boolean does, as well as showing the default values from the config.

If you are fine with this I can create an additional PR with those changes.

I think that users who are not comfortable with tests, etc. will not look into those, and you do not want to digg through tests just to figure out what a package does.

Worst scenario, people just don't use the package, which would be sad, as it is a really good one.

This would fix #28

@lukasoppermann lukasoppermann mentioned this pull request Aug 26, 2016
@@ -1,7 +1,9 @@
Laravel Binput
==============

Laravel Binput was created by, and is maintained by [Graham Campbell](https://github.com/GrahamCampbell), and is an input protector for [Laravel 5](http://laravel.com). It utilises my [Laravel Security](https://github.com/GrahamCampbell/Laravel-Security) package. Feel free to check out the [change log](CHANGELOG.md), [releases](https://github.com/GrahamCampbell/Laravel-Binput/releases), [license](LICENSE), and [contribution guidelines](CONTRIBUTING.md).
Laravel Binput was created by, and is maintained by [Graham Campbell](https://github.com/GrahamCampbell), and is an input protector for [Laravel 5](http://laravel.com) that strips unwanted elements, e.g. `<script>` tags from any input you receive. It utilises my [Laravel Security](https://github.com/GrahamCampbell/Laravel-Security) package.
Copy link
Owner

Choose a reason for hiding this comment

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

Hmm, this description isn't quite true.

Copy link
Author

Choose a reason for hiding this comment

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

I might have misunderstood something. 😉 Please let me know what I should change.

Copy link
Owner

Choose a reason for hiding this comment

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

It prevents them doing damage rather than removing all traces of them.

@lukasoppermann
Copy link
Author

Will change it once I am back at my notebook.

I think this could make it easier to understand. I would also add an example to clarify what the `xss` boolean does, as well as showing the default values from the config.

If you are fine with this I can create an additional PR with those changes.

I think that users who are not comfortable with tests, etc. will not look into those, and you do not want to digg through tests just to figure out what a package does.

Worts scenario, people just don't use the package, which would be sad, as it is a really good one.
@lukasoppermann
Copy link
Author

Hey @GrahamCampbell, I updated the text, do you think this now reflects the reality better?

@lukasoppermann
Copy link
Author

Hey @GrahamCampbell what do you think, can this be merged, or would you need something change first?

@GrahamCampbell GrahamCampbell merged commit e7e6223 into GrahamCampbell:master Dec 27, 2016
@GrahamCampbell
Copy link
Owner

Thanks. I'll tweak it myself now.

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.

Extend the readme
2 participants