Skip to content

fix: Keep track of synthetic apify-default-dataset-item events #528

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
Draft
janbuchar wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

fix: Keep track of synthetic apify-default-dataset-item events #528

janbuchar wants to merge 2 commits into from
+177 −21

Conversation

@janbuchar
Copy link
Contributor

@janbuchar janbuchar commented Dec 12, 2025 •
edited
Loading

@janbuchar janbuchar added the t-tooling Issues with this label are in the ownership of the tooling team. label Dec 12, 2025
@janbuchar
Copy link
Contributor Author

janbuchar commented Dec 12, 2025

@mhamas @metalwarrior665 this proved to be way more complicated than previously thought. I'll try to simplify it on Monday.

@janbuchar
Copy link
Contributor Author

janbuchar commented Dec 12, 2025

An alternative solution to this could be just screaming bloody murder in case that there is a nonzero price for apify-default-dataset-item and another event type is present in the configuration. This would force the developer to start using a custom event to charge for dataset items. It is possible to implement it on the SDK level as well as on platform.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

t-tooling Issues with this label are in the ownership of the tooling team.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Track the number of apify-default-dataset-item events locally

2 participants

@janbuchar