Aayush Optimize Field Dependency & Selection Flow#4806
Aayush Optimize Field Dependency & Selection Flow#4806one-community merged 4 commits intodevelopmentfrom
Conversation
✅ Deploy Preview for highestgoodnetwork-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
one-community
added
the
High Priority - Please Review First
rohanrastogi311
left a comment
rohanrastogi311
left a comment
There was a problem hiding this comment.
Hi Aayush,
Can't select equipment.
Anusha-Gali
left a comment
Anusha-Gali
left a comment
There was a problem hiding this comment.
Hi Aayush,
I have reviewed your PR locally and would like to point out two issue.
- The requirement mentioned that the dropdown's should be disabled until prerequisite selections are made, but i am able to select tool before project - let me know if it is to be allowed
- Upon selecting equipment, unable to select any name and update it.
4806.mov
|
The field itemType used to populate the equipment is coming back as null in the response. Because of that, there’s no data for the frontend to render. I’ve added a fallback so the UI handles this case gracefully (No name available), and if this field is expected to contain values, the issue is upstream in the API response or data. |
|
|
Thank you all, merging! |
4 participants
Description
Related PRS (if any):
…
Main changes explained:
…
How to test:
npm installand...to run this PR locallyNote:
No equipments available is a fallback for no data in API response
Screenshots or videos of changes:
Recording.2026-02-07.025910.mp4