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

Fix access token revoking #3131

Merged
merged 3 commits into from Jun 11, 2019
Merged

Fix access token revoking #3131

merged 3 commits into from Jun 11, 2019

Conversation

rhymes
Copy link
Contributor

@rhymes rhymes commented Jun 11, 2019

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Documentation Update

Description

I'm not 100% sure why but it seems that putting the ID as a keyword parameter for a DELETE does not play nice with Rails. I've converted it to use an inline parameter following the same convention Rails uses for any other DELETE/destroy action

Related Tickets & Documents

Closes #3079

Added to documentation?

  • docs.dev.to
  • readme
  • no documentation needed

@pr-triage pr-triage bot added the PR: unreviewed bot applied label for PR's with no review label Jun 11, 2019
@pr-triage pr-triage bot added PR: reviewed-approved bot applied label for PR's where reviewer approves changes and removed PR: unreviewed bot applied label for PR's with no review labels Jun 11, 2019
@benhalpern benhalpern merged commit e48c966 into forem:master Jun 11, 2019
@pr-triage pr-triage bot added PR: merged bot applied label for PR's that are merged and removed PR: reviewed-approved bot applied label for PR's where reviewer approves changes labels Jun 11, 2019
@rhymes rhymes deleted the rhymes/fix-access-token-revoking branch June 13, 2019 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: merged bot applied label for PR's that are merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: revoking an acess token resulting in a 404
2 participants