search

ratifire / devrate-service

1 stars 0 forks source link

[BE]Specializations: When a user adds a specialization for the first time, it is added to the top bar with a level of "NaN"/ коли користувач додає спеціалізацію вперше, вона додається до верхньої панелі з level "NaN" (№ K-22) #362

Closed KhanAnna closed 3 months ago

KhanAnna commented 3 months ago

Steps to reproduce

  1. Go to the URL.
  2. Log in.
  3. Press the profile button on the top panel
  4. In the drop-down menu, select the "Specialization" tab
  5. Сlick the add specialization button in the form +
  6. Fill in fields name of specialization and level of specialization
  7. Click the save button

Actual results When a user adds a specialization for the first time, it is added to the top bar with a level of "NaN", after refreshing the page "level" is added.

Expected results Added specialization. The name and level correspond to what was created

https://github.com/user-attachments/assets/d30a8722-fdb0-4cdc-8ae6-4c139d9e2c7f

Image

IvashchenkoIvanIgorevich commented 3 months ago

I tried to reproduce the bug by following the steps, but the bug did not occur. I was testing from the main branch; maybe the bug has already been fixed within the scope of other bugs. @KhanAnna can you please retest it?

https://github.com/user-attachments/assets/de47f521-5a67-4214-b049-78285cec4ec7

KhanAnna commented 3 months ago

https://drive.google.com/file/d/1bEUCVPY2Dqn8gXbA351m6L1fHfYtIOnU/view?usp=sharing video does not add due to weight restrictions @IvashchenkoIvanIgorevich

KhanAnna commented 3 months ago

this error only occurs when you first add a specialization after starting the server

Steps to reproduce

  1. new - restart server (docker)
  2. Go to the URL.
  3. Log in.
  4. Press the profile button on the top panel
  5. In the drop-down menu, select the "Specialization" tab
  6. Сlick the add specialization button in the form +
  7. Fill in fields name of specialization and level of specialization
  8. Click the save button
BlackPuma9 commented 3 months ago

Hi @KhanAnna and @IvashchenkoIvanIgorevich,

I've just pushed changes into main branch that might help to fix the bug. I've tested from my side a couple of times and for me mentioned behaviour in the beginning not applicable.

Could you please test again and let me know if issue still persist?

Thank you!

Yuliia