Skip to content

Conversation

@freekvandeven
Copy link
Contributor

No description provided.

@mighttymike mighttymike force-pushed the feature/bouwadvies-stepper-updates branch from 0151686 to 9e86b90 Compare May 13, 2025 13:49
@override
Widget build(BuildContext context) {
var step = steps[index];
if (currentStep - 1 > index && stepperTheme.hideStepWhenDone) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I find it weird why the currentStep is offset by one. I pretty sure this is all through the package which I find weird.

Apart from that I think the currentStep should be provided with the offset removed when provided as parameter instead in this widget.

if (showOnlyCurrentStep) ...[
SizedBox(
height: index == steps.length - 1 ? 0 : stepperTheme.emptyHeight,
height: index == steps.length - 1 ? 0 : lineHeight,
Copy link
Contributor

Choose a reason for hiding this comment

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

This is confusing. I have a different thought with the term "lineHeight" then "emptyHeight" but is used the same way.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think we can change this back

child: Column(
children: [
GestureDetector(
onTap: () {},
Copy link
Contributor

Choose a reason for hiding this comment

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

Does this serve any purpose?

currentStep: currentIndex,
lineHeight: currentIndex > index &&
stepperTheme.hideStepWhenDone
? 40
Copy link
Contributor

Choose a reason for hiding this comment

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

Using a hard value. Could this be a problem with implementations in other projects?

Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be a new test instead of changing an existing one?

Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't we start splitting this file up in different files?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

maybe

Copy link
Contributor Author

@freekvandeven freekvandeven left a comment

Choose a reason for hiding this comment

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

good

@freekvandeven freekvandeven self-assigned this May 28, 2025
@freekvandeven freekvandeven marked this pull request as ready for review May 28, 2025 13:39
@freekvandeven freekvandeven changed the title WIP: Stepper Updates Stepper updates for flutter_configurator May 28, 2025
@freekvandeven freekvandeven merged commit 9b59e1c into master May 28, 2025
1 check passed
@freekvandeven freekvandeven deleted the feature/bouwadvies-stepper-updates branch May 28, 2025 13:42
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.

3 participants