Skip to content

Add step-based progress tracking#9

Closed
insign wants to merge 1 commit intomainfrom
feature/step-based-progress-8495322058049971929
Closed

Add step-based progress tracking#9
insign wants to merge 1 commit intomainfrom
feature/step-based-progress-8495322058049971929

Conversation

@insign
Copy link
Contributor

@insign insign commented Feb 14, 2026

This change introduces step-based progress tracking to the Progressable trait. It allows users to define the total number of steps and increment the current step, automatically calculating the progress percentage. This is useful for tasks where the number of items is known.


PR created automatically by Jules for task 8495322058049971929 started by @insign

- Added `setTotalSteps`, `incrementStep`, `setStep` methods.
- Added `totalSteps` and `currentStep` properties.
- Added tests for step-based progress tracking.
@google-labs-jules
Copy link

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 770b9141da

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

if ($steps <= 0) {
throw new \InvalidArgumentException('Total steps must be greater than 0');
}
$this->totalSteps = $steps;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reset step state when redefining total steps

Calling setTotalSteps() updates only totalSteps and leaves currentStep untouched, so reusing the same instance for a new task carries over the old step counter. In that scenario, the next incrementStep() computes progress from stale state (often jumping straight to 100%), which makes the new run report incorrect progress data.

Useful? React with 👍 / 👎.

if ($this->totalSteps === null) {
throw new \LogicException('Total steps not set. Call setTotalSteps() first.');
}
$this->currentStep = $step;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reject negative step values in step-based APIs

setStep() accepts negative integers and stores them directly in currentStep, which can produce an invalid negative step count while local progress is clamped to 0. This creates inconsistent state (getCurrentStep() negative, getLocalProgress() non-negative) and can skew subsequent step calculations if a caller passes a computed value below zero.

Useful? React with 👍 / 👎.

@insign insign closed this Feb 16, 2026
@insign insign deleted the feature/step-based-progress-8495322058049971929 branch February 16, 2026 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments