You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
additionally callback is a reserved word, in a sense it is a descriptive term well known in IT.
for all these reasons, id like to rename it. following changes would apply
callback passed to FederatedServiceRouter should be named redirectURL/redirectURI, because it is the copied value from the oauth provider named redirect_uri .
callback function which handles the route for the redirect_uri, would be named handleoauthRedirect
files representing related content, GoogleCallbackBody.swift´, would be renamed to GoogleOauthRedirectBody.swift`
furthermore what is the background behind those static references?
variable representing the redirectURL, which is dictated by the oauth2 provider.
is named callback.
example:
a few router have a callbackURL, representing the same thing this hardcoded. example:
on top a function which handles the "callback" made on the "callback" sometimes referred to as "callbackURL" is named... you guessed it. "callback"
additionally callback is a reserved word, in a sense it is a descriptive term well known in IT.
for all these reasons, id like to rename it. following changes would apply
redirectURL
/redirectURI
, because it is the copied value from the oauth provider namedredirect_uri
.redirect_uri
, would be namedhandleoauthRedirect
GoogleCallbackBody.swift´, would be renamed to
GoogleOauthRedirectBody.swift`furthermore what is the background behind those static references?
the auth url could only be wrong for it would not be dictated by the provider.
this ill let be, for the moment...
all is open for discussion! please let me know what you thing, your input and thoughts.
The text was updated successfully, but these errors were encountered: