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
Too many people ask "How do I do this?" questions, for which they should be just looking at the Graph API documentation / asking on Stack Overflow and then just writing the equivalent FB.api call for.
The sample app is also probably better off dead. This is a library and so a full fledged html app does not help demonstrate how to make api calls. Examples are better off short like those in the README.
However I suppose we could add more in-depth code samples that instead of abstractly documenting how to make API calls give examples of actual API calls that can actually be run.
Instead of the readme these could live in a SAMPLES.md.
The samples doc could point you to creating a sample app to get and API key and secret. As well as using Facebook's own Graph API Explorer to grab an access token.
As a bonus, we could probably link to the samples page through RunKit (https://runkit.com/npm/fb/SAMPLES.md) to allow people to run samples themselves. And/or we can create our own "Notebooks" on the site and link to them from each sample. Apparently RunKit allows for users to define environment variables with API keys, so we can make use of that to allow people to create their own Facebook sample apps.
However to force RunKit to use the right versions in examples we may have to either use require('[email protected]') syntax in the samples and automatically update them each new version. Or use the RunKit api to automatically create a "Notebook" for each new release, replacing old ones each release so RunKit uses the latest version.
Too many people ask "How do I do this?" questions, for which they should be just looking at the Graph API documentation / asking on Stack Overflow and then just writing the equivalent
FB.api
call for.The sample app is also probably better off dead. This is a library and so a full fledged html app does not help demonstrate how to make api calls. Examples are better off short like those in the README.
However I suppose we could add more in-depth code samples that instead of abstractly documenting how to make API calls give examples of actual API calls that can actually be run.
Instead of the readme these could live in a
SAMPLES.md
.The samples doc could point you to creating a sample app to get and API key and secret. As well as using Facebook's own Graph API Explorer to grab an access token.
As a bonus, we could probably link to the samples page through RunKit (https://runkit.com/npm/fb/SAMPLES.md) to allow people to run samples themselves. And/or we can create our own "Notebooks" on the site and link to them from each sample. Apparently RunKit allows for users to define environment variables with API keys, so we can make use of that to allow people to create their own Facebook sample apps.
However to force RunKit to use the right versions in examples we may have to either use
require('[email protected]')
syntax in the samples and automatically update them each new version. Or use the RunKit api to automatically create a "Notebook" for each new release, replacing old ones each release so RunKit uses the latest version.The text was updated successfully, but these errors were encountered: