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.
This pull request introduces a new
PlanStepStatus
enum class to standardize the statuses of plan steps and updates the codebase to use this enum instead of hardcoded status strings. The changes improve code readability and maintainability by centralizing the status definitions and related utility methods.Key changes include:
Introduction of
PlanStepStatus
Enum:app/flow/base.py
: AddedPlanStepStatus
enum class with possible statuses (NOT_STARTED
,IN_PROGRESS
,COMPLETED
,BLOCKED
) and utility methods (get_all_statuses
,get_active_statuses
,get_status_marks
).Refactoring to Use
PlanStepStatus
:app/flow/planning.py
: Updated imports to includePlanStepStatus
.app/flow/planning.py
: Replaced hardcoded status strings withPlanStepStatus
values in_get_current_step_info
,_mark_step_completed
, and_generate_plan_text_from_storage
methods. [1] [2] [3] [4] [5] [6]FeaturesFeature Docs
Influence
Result
Other