doc: remove mention of old benchmark method reference#2286
Merged
triceo merged 2 commits intoTimefoldAI:mainfrom May 5, 2026
Merged
doc: remove mention of old benchmark method reference#2286triceo merged 2 commits intoTimefoldAI:mainfrom
triceo merged 2 commits intoTimefoldAI:mainfrom
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the benchmarking documentation to remove a reference to the old PlannerBenchmark.benchmarkAndShowReportInBrowser() API and align the examples with the current benchmark() method in the benchmarker docs.
Changes:
- Replaced outdated benchmark API calls in two Java examples.
- Kept the surrounding benchmarking guidance and report-generation explanation intact.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
triceo
approved these changes
May 5, 2026
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
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.
Was in our migration recipe, but was still mentioned in the docs.