Ringrev / facebook-api-rs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Update the token struct to have a type and update Client to manage eveyr kind of token

arn-the-long-beard opened this issue · comments

Overview of feature 📝

From our discussion we Duke, we understood that we only need one token at a time. So we could use the same struct for every token. Expiration for page page_access_token is set depending for the user access token life duration, so the api should fix it for the user.

Client accept every token. Type of the token is set on the struct.

Which problem is the feature or enhancement solving❓

It helps us to improve the api by removing confusion on the actually use of it because we pass empty user access token to client when we use pages apis.

Documentation & Help ℹ️

The method to allow developers to choose which token they want used to make facebook api or the token they want to create for facebook page has been added.
Although this does not change the fact that the user tokens ( short and long live ) is already available, but they can chose to create a short or long live token for the pages access