Skip to content

Conversation

@michel-m
Copy link
Contributor

Hello,
We would like to be able to use django-oauth-toolkit for our project, but unfortunately we use very different kinds of models and the validator doesn't fit our needs.
As suggests this pull request, we would like to be able to specify as a setting the class used for the validator (along with the models used by this validator).
We hope you will find it convenient.
Anyhow, thanks for the good work.
Have a good day,
M

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 645680d on michel-m:settings_validator_class into 74012ef on evonove:master.

@synasius
Copy link
Contributor

Hi @michel-m

thnx for your PR. This partly solves issue #19

It's good to merge, just solve what outlined in previous comments

Thnx 👍

reinout and others added 2 commits October 24, 2013 18:03
Most of the bullet lists where shown as blockquotes because they were indented one space.

To keep the version numbers in the changelog stand out (now that there wasn't a blockquote beneath them anymore) I turned them into h3 items.
@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling d102b4d on michel-m:settings_validator_class into 74012ef on evonove:master.

@michel-m
Copy link
Contributor Author

Updated.
Though, using git rebase -i (fixup on last commit and reword on first), I think it messed with the last commit on master. Should I create a new, clean, branch?

@masci
Copy link
Contributor

masci commented Oct 24, 2013

@michel-m yep, rebasing changed one commit on your repo and it shouldn't be pushed. If you could create a clean PR it would be great!
TIA

@michel-m michel-m closed this Oct 25, 2013
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.

5 participants