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
Thank you for this! Amazing and beautiful work. I though I`d share my minor findings in the UI / UX. Nothing major..
Is your feature request related to a problem? Please describe.
This is not related to a problem.
Describe the solution you'd like
Some UI texts are misleading regarding credit usage of ScrapingAnt. The credit usage text should reflect what is selected in the configuration.
Describe alternatives you've considered
None
Additional context
Below it should be residential
In the job overview, the current usage of credits is shown. It should reflect the configuration (datacenter) and display 10 credits/ call instead of 250.
I also checked ScrapingAnt website to check why premium is 250 credits. I could not find it. Should it rather be 125 ?
The text was updated successfully, but these errors were encountered:
Hey. Thanksgiving for the report. It seems like scrapingant has recently changed the credit system.
I'm going to adapt the texts, it just might take a while as I am currently in the hospital.
Get back to you once done :)
Thank you for this! Amazing and beautiful work. I though I`d share my minor findings in the UI / UX. Nothing major..
Is your feature request related to a problem? Please describe.
This is not related to a problem.
Describe the solution you'd like
Some UI texts are misleading regarding credit usage of ScrapingAnt. The credit usage text should reflect what is selected in the configuration.
Describe alternatives you've considered
None
Additional context
Below it should be
residential
In the job overview, the current usage of credits is shown. It should reflect the configuration (
datacenter
) and display 10 credits/ call instead of 250.I also checked ScrapingAnt website to check why premium is 250 credits. I could not find it. Should it rather be 125 ?
The text was updated successfully, but these errors were encountered: