Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Show friendly user message when we hit GA quota limit #67

Open
mgechev opened this issue Jul 25, 2018 · 3 comments
Open

Show friendly user message when we hit GA quota limit #67

mgechev opened this issue Jul 25, 2018 · 3 comments
Assignees
@mgechev
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@mgechev
Copy link
Member

mgechev commented Jul 25, 2018

No description provided.

@mgechev mgechev added the enhancement New feature or request label Jul 25, 2018
@mgechev mgechev self-assigned this Jul 25, 2018
@addyosmani
Copy link
Contributor

Should we also point to a URL for requesting a bump in quota?

@mgechev mgechev mentioned this issue Nov 20, 2018
Open
@rockeynebhwani rockeynebhwani mentioned this issue Jan 19, 2019
Closed
@mgechev mgechev added help wanted Extra attention is needed good first issue Good for newcomers labels Sep 26, 2019
@Coly010
Copy link

Coly010 commented Sep 26, 2019

What are i18n and l10n requirements for the friendly message?

@mgechev
Copy link
Member Author

mgechev commented Sep 26, 2019 •
edited
Loading

I think, for now, it's good enough to catch & detect the error that guess-ga throws when guess-webpack requests a report and display an error message that the user has exceeded the rate limit + a URL for requesting a bump in quota.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mgechev mgechev

Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@addyosmani @mgechev @Coly010