feat(core): add statisticsStateSchema option for custom metrics#3554
Open
feat(core): add statisticsStateSchema option for custom metrics#3554
Conversation
…into custom-stats-v4
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
add statisticsStateSchema to BasicCrawlerOptions to allow passing a custom zod schema.
this allows developers to extend the statistics state with strict typing and disk persistence.
eliminate the need to manually subclass the internal statistics engine for custom metrics.
update AdaptivePlaywrightCrawlerStatistics constructor to deeply merge schemas.
prevent zod's strip behavior from deleting required framework metrics during serialization.
add comprehensive vitest coverage to ensure custom schemas are tracked across all crawlers.
Closes #3525