Skip to content
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

Open
shivankacker opened this issue Nov 5, 2024 · 8 comments · May be fixed by #9270
Open

Fix UI bugs with Symptoms editor and move to ModelCrudEditor component #8998

shivankacker opened this issue Nov 5, 2024 · 8 comments · May be fixed by #9270

Comments

@shivankacker
Copy link
Member

shivankacker commented Nov 5, 2024

Image

@Keerthilochankumar
Copy link
Contributor

I want to work on this issue. assign it to me.

@SwanandBhuskute
Copy link
Contributor

I would like to work on this @shivankacker

@Srayash
Copy link
Contributor

Srayash commented Nov 5, 2024

hey @shivankacker @rithviknishad I've made a PR fixing the UI issues, but I'll need some help with implementing the move to ModelCrudEditor part.

@shivankacker
Copy link
Member Author

@Srayash sure what's the blocker?

@Srayash
Copy link
Contributor

Srayash commented Nov 6, 2024

@Srayash sure what's the blocker?

Hi @shivankacker, I truly appreciate your willingness to help.
I'm a bit uncertain about the approach to take. If you could kindly share any insights on how to tackle this, I would be incredibly grateful for your support.

Thank you for your time and assistance!

@shivankacker
Copy link
Member Author

shivankacker commented Nov 6, 2024

@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.

@Srayash
Copy link
Contributor

Srayash commented Nov 8, 2024

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!

@JavidSumra
Copy link
Contributor

Hey Team I would like to work on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment