Skip to content

Add docs about console question answer normalizing. #7125

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

Conversation

SpacePossum
Copy link
Contributor

Add description about how to use normalizing on an answer given on a question in a console application.

@HeahDude
Copy link
Contributor

👍

Status: Reviewed

Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

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

👍

@SpacePossum I love it when we add docs for undocumented features. Thanks a lot!

I made some rewordings to your original text to match the style of the rest of the documentation. If you don't agree with something, please tell us!

@SpacePossum
Copy link
Contributor Author

thanks @javiereguiluz for fixing the wording, all good :)
👍

@xabbuh
Copy link
Member

xabbuh commented Nov 28, 2016

Thank you @SpacePossum.

@xabbuh xabbuh closed this Nov 28, 2016
xabbuh added a commit that referenced this pull request Nov 28, 2016
…ePossum, javiereguiluz)

This PR was submitted for the 2.8 branch but it was merged into the 2.7 branch instead (closes #7125).

Discussion
----------

Add docs about console question answer normalizing.

Add description about how to use normalizing on an answer given on a question in a console application.

Commits
-------

5e39973 Minor rewords in the text and the code example
2cae22f Update questionhelper.rst
5f81796 Add docs about console question answer normalizing.
@SpacePossum SpacePossum deleted the 2_8_Question_Helper_add_normalizer_sample branch November 28, 2016 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants