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

Document how to work with custom parsers #36

Open
mpscholten opened this issue Aug 17, 2016 · 3 comments
Open

Document how to work with custom parsers #36

mpscholten opened this issue Aug 17, 2016 · 3 comments
Assignees
Milestone

Comments

@mpscholten
Copy link
Owner

mpscholten commented Aug 17, 2016

E.g. when dealing with a custom value object A it might make sense to create your own ->param(..)->a()->required().

We should add documentation on how to do that and maybe change code to make the process easier.

TODO:

  • Creating your own AParser
  • Extending TypeParser with ->a()
  • Configuring the library to use the custom TypeParser
@mpscholten mpscholten added this to the v1.4 milestone Aug 17, 2016
@mpscholten mpscholten self-assigned this Aug 17, 2016
@yuvalherziger
Copy link
Collaborator

Nice 👍
We could even add a CLI script that can be run à la:

$ /scripts/generate custom-parser -c AParser
### and also for custom exceptions:
$ /scripts/generate custom-exception -c AException

@mpscholten
Copy link
Owner Author

Great suggestion :) Could you open an issue for that?

@apeiniger
Copy link

+1 for custom types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants