-
Notifications
You must be signed in to change notification settings - Fork 119
core: frontend: wizard: rover/BOAT exists but no boat/UNDEFINED #3679
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.
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
core: frontend: wizard: rover/BOAT exists but no boat/UNDEFINED #3679
Conversation
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideUpdates the wizard component to initialize the boat_model using the correct rover/BOAT model instead of the previous boat/UNDEFINED model, aligning the frontend with the expected configuration semantics for boats in the wizard flow. Class diagram for updated Wizard Vue component data initializationclassDiagram
class WizardComponent {
+boat_model any
+scripts string[]
+configuration_failed boolean
+error_message string
+data()
}
class ModelFactory {
+get_model(category string, name string) any
}
WizardComponent ..> ModelFactory : uses get_model
%% Updated initialization:
%% boat_model = get_model(rover, BOAT) instead of get_model(boat, UNDEFINED)
File-Level Changes
Assessment against linked issues
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey there - I've reviewed your changes - here's some feedback:
- Now that
boat_modelis initialized fromget_model('rover', 'BOAT'), consider renaming the variable to better reflect that it holds a rover/BOAT model to avoid future confusion. - If other parts of the wizard still expect a
boattype rather thanrover, double-check that this change doesn't introduce mismatches in downstream use ofboat_model(e.g., in conditionals or templates) and align naming/type expectations accordingly.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Now that `boat_model` is initialized from `get_model('rover', 'BOAT')`, consider renaming the variable to better reflect that it holds a rover/BOAT model to avoid future confusion.
- If other parts of the wizard still expect a `boat` type rather than `rover`, double-check that this change doesn't introduce mismatches in downstream use of `boat_model` (e.g., in conditionals or templates) and align naming/type expectations accordingly.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
Fix #3678
Summary by Sourcery
Bug Fixes: