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

as_string doesn't work on fields.Integer #173

Closed
taion opened this Issue Mar 17, 2015 · 0 comments

Comments

Projects
None yet
2 participants
@taion
Contributor

taion commented Mar 17, 2015

fields.Integer(as_string=True).as_string == False

This is a trivial fix and I'll submit a preliminary PR shortly.

I am confused by the following things, however:

  1. Why are the non-kwargs arguments on Integer other than default duplicated with the same value as on Number?
  2. Why is the documentation for as_string not on Number?
  3. Is it intentional that attribute and error are not accepted as positional args for Decimal?

taion added a commit to taion/marshmallow that referenced this issue Mar 17, 2015

@taion taion changed the title from as_string is strange and broken to as_string doesn't work on fields.Integer Mar 17, 2015

@sloria sloria closed this Mar 17, 2015

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