[PR #186] [MERGED] made oauth_verifier public on OAuthSwiftCredential #552

New issue

Closed

opened 2026-03-03 16:49:24 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 16:49:24 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/OAuthSwift/OAuthSwift/pull/186
Author: @almostintuitive
Created: 2/18/2016
Status: ✅ Merged
Merged: 2/18/2016
Merged by: @phimage

Base: master ← Head: oauth-verifier-made-public

📝 Commits (2)

6f97237 made oauth_verifier public on OAuthSwiftCredential
fd583d8 make OAuthSwiftCredential.oauth_verifier read-only outside of the framework

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 OAuthSwift/OAuthSwiftCredential.swift (+1 -1)

📄 Description

Hi,
Thanks for the awesome work again! We found OAuthSwift super useful.

We have been working on a project where the backend requires us to send the "oauth_verifier" to the server after a user has authenticated.
I consulted with the backend guys and they said this requirement is coming from the official Flickr library they're using.
Would it be alright to expose this property as public? Are there any other workarounds we could use to access it without necessarily polluting the public API? Has this been requested before?

Thanks a lot!

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/OAuthSwift/OAuthSwift/pull/186 **Author:** [@almostintuitive](https://github.com/almostintuitive) **Created:** 2/18/2016 **Status:** ✅ Merged **Merged:** 2/18/2016 **Merged by:** [@phimage](https://github.com/phimage) **Base:** `master` ← **Head:** `oauth-verifier-made-public` --- ### 📝 Commits (2) - [`6f97237`](https://github.com/OAuthSwift/OAuthSwift/commit/6f972376f2667c9212572fcb86d6e55a749dcf48) made oauth_verifier public on OAuthSwiftCredential - [`fd583d8`](https://github.com/OAuthSwift/OAuthSwift/commit/fd583d81f41d3d34819e4947e109382d0ade2608) make OAuthSwiftCredential.oauth_verifier read-only outside of the framework ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `OAuthSwift/OAuthSwiftCredential.swift` (+1 -1) </details> ### 📄 Description Hi, Thanks for the awesome work again! We found OAuthSwift super useful. We have been working on a project where the backend requires us to send the "oauth_verifier" to the server after a user has authenticated. I consulted with the backend guys and they said this requirement is coming from the official Flickr library they're using. Would it be alright to expose this property as public? Are there any other workarounds we could use to access it without necessarily polluting the public API? Has this been requested before? Thanks a lot! --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>