Nebular: NbStep ignoring [completed] when the next step is clicked

Created on 18 Sep 2018  路  6Comments  路  Source: akveo/nebular

Issue type

I'm submitting a ...

  • [X] bug report
  • [ ] feature request

Issue description

When passing the parameter completed to NbStep (<nb-step [completed]="false"></nb-step>, the step is marked as completed when another step is selected by clicking on the step number, even if the value of competed is false.

Expected behavior:

When passing the value of completed the step should be set as completed only if the value is true.

Steps to reproduce:

  • Create a stepper with at lease to steps;
  • Set completed to false for the first step.
  • Click on the second step.
  • Notice that the first step is marked as completed.
important theme

Most helpful comment

Hello i have the same problem, an example:

let stockValid = false;

never change this variable, but if i change to the next or another step, this step "Stock" is checked like a complete the same way.

Please can fix that?

Thanksyou

All 6 comments

Hello @ilDon.
I can't reproduce this issue. Could you create a working example on stackblitz?
Thanks!

Closing as it's been a while.

Same problem

Hello i have the same problem, an example:

let stockValid = false;

never change this variable, but if i change to the next or another step, this step "Stock" is checked like a complete the same way.

Please can fix that?

Thanksyou

Same problem here while fixing

i made this fix:
[completed]="indirectTasksHasCompleted()"
[stepControl]="{valid: indirectTasksHasCompleted(), reset: null}">

Create a inline object with key valid and reset.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bnbs picture bnbs  路  4Comments

aqsdc1 picture aqsdc1  路  3Comments

ChristianVega5421 picture ChristianVega5421  路  3Comments

andredatsch picture andredatsch  路  3Comments

rhajizadeh picture rhajizadeh  路  3Comments