John Cass
John Cass
A lot of this has since landed in 'develop' (except for the user delete signaling). If you could rebase this PR on 'develop' the maintainers might be able to take...
Pushed 19f61a53cb12fe2a4b0a3abfcece233f38a217f5, with changes from 'develop' merged in.
According to the Stormpath specification: > If the error is created by the framework integration (it is not from the REST API), then use status 400 and a human-friendly message...
@rdegges, anything else that you would like to see addressed here?
This might best be done using Flask's `before_request` decorator as discussed at http://stackoverflow.com/questions/13428708/best-way-to-make-flask-logins-login-required-the-default. Not sure this is something that needs to go into the flask-stormpath core though as there are...
This was fixed with #90 when we switched from using ``Form`` to ``FlaskForm``. Have you tried using the 'develop' branch to see if that works for you? @rdegges, it might...
There may be two separate issues here: the ``TypeError: __init__() takes from 1 to 2 positional arguments but 7 were given`` that @dappiu reported should not be a problem in...
Ah I see. #94 seems to fixe the remaining issues with the /register page.
@rdegges, do you think we can configure the repository to use 'develop' as the default branch instead of 'master'? Apart from allowing us to close issues automatically via commit messages...
Thanks for the PR. Any chance of getting some test coverage based on `default` and custom database configurations?