-
Notifications
You must be signed in to change notification settings - Fork 451
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
Fix UI bugs with Symptoms editor and move to ModelCrudEditor component #8998
Comments
I want to work on this issue. assign it to me. |
I would like to work on this @shivankacker |
hey @shivankacker @rithviknishad I've made a PR fixing the UI issues, but I'll need some help with implementing the |
@Srayash sure what's the blocker? |
Hi @shivankacker, I truly appreciate your willingness to help. Thank you for your time and assistance! |
@Srayash I have mentioned an example of the ModelCrudEditor component. It is basically a helper component to create modules where you need to create/edit/delete rows (just like symptoms editor). All you will have to do is port the existing component. If you spend some time on it you would understand how the component works. |
Hi @@shivankacker - I wanted to update you on my progress. I've completed part of the task but have hit some roadblocks. The ported component isn't functioning as expected yet. I'll submit a draft PR with my current work so you can review it and help guide me on completing the remaining portions and fixing the component's behavior. Thanks! |
Hey Team I would like to work on it. |
<EncounterSymptomsBuilder>
component to use<ModelCrudEditor>
Example:
care_fe/src/components/Facility/SpokeFacilityEditor.tsx
Line 132 in a0e6e62
The text was updated successfully, but these errors were encountered: