-
Notifications
You must be signed in to change notification settings - Fork 35
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.
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
Feature/rate limiting2 #1667
Feature/rate limiting2 #1667
Conversation
], | ||
autoform: { | ||
options: { | ||
custom: 'Custom rate limits', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember to add i18n to these texts.
'rate_limits.$.duration': { | ||
type: Number, | ||
optional: true, | ||
label: 'Duration (ms)', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember i18n here.
], | ||
autoform: { | ||
options: { | ||
apiKey: 'API Key', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember i18n here.
'rate_limits.$.limit': { | ||
type: Number, | ||
optional: true, | ||
label: 'Number of requests', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember i18n here.
'rate_limits.$.response_headers': { | ||
type: Boolean, | ||
optional: true, | ||
label: 'Show rate limit in response headers', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remember i18n here.
Reviewer, added RateLimit schema, cause sub-field translations did not otherwise work. |
This works, but does not alert the end-user of success. There was an sAlert onSuccess for the autoform, at one point. |
This is also allowing the same data to be submitted multiple times to API Umbrella, causing duplicate entries in the API Umbrella Backends collection. It is probably related to the form not entering a 'success' state, which would also prevent the onSuccess callback from firing. |
@brylie Could you help to reproduce issues mentioned above? |
@brylie Discussion summary attached Required changes
|
I will merge this. @jykae please also open an enhancement describing your idea for improving the duration field to allow user to use 'minutes', 'hours', etc. |
Closes #1190