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
Hello OERPub team. I ran into this issue today and figured it would have been nice to receive some sort of warning / notification without having to dig into Chrome dev tools. When I went to demo the book editor without logging into my Github account, I hit their rate limit:
{
message: "API rate limit exceeded for XXX.XXX.XXX.XXX. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
documentation_url: "http://developer.github.com/v3/#rate-limiting"
}
The current behavior in the UI is to tell the user that the demo-book bookshelf is invalid (please select another), which was confusing and not entirely accurate...
The text was updated successfully, but these errors were encountered:
Hello OERPub team. I ran into this issue today and figured it would have
been nice to receive some sort of warning / notification without having to
dig into Chrome dev tools. When I went to demo the book editor without
logging into my Github account, I hit their rate limit:
{
message: "API rate limit exceeded for XXX.XXX.XXX.XXX. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
documentation_url: "http://developer.github.com/v3/#rate-limiting"
}
The current behavior in the UI is to tell the user that the demo-book
bookshelf is invalid (please select another), which was confusing and not
entirely accurate...
Reply to this email directly or view it on GitHubhttps://github.com//issues/160
.
Hello OERPub team. I ran into this issue today and figured it would have been nice to receive some sort of warning / notification without having to dig into Chrome dev tools. When I went to demo the book editor without logging into my Github account, I hit their rate limit:
The current behavior in the UI is to tell the user that the demo-book bookshelf is invalid (please select another), which was confusing and not entirely accurate...
The text was updated successfully, but these errors were encountered: