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.

Sign up for GitHub

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

Jump to bottom

Refactor code in Atomic/Scenario/Report/Simulation Popover #2610

Open
savacano28 opened this issue Mar 5, 2025 · 0 comments
Open

Refactor code in Atomic/Scenario/Report/Simulation Popover #2610

savacano28 opened this issue Mar 5, 2025 · 0 comments
Labels
needs triage use to identify issue needing triage from Filigran Product team technical improvement Technical refactor or improvement is needed

Comments

@savacano28
Copy link
Contributor

Description

Currently, We have the following components: Atomic/Scenario/Report/Simulation Popover with duplicated code, so We want to refactor them to elimanate redundancy.

Environment

  1. Obas Frontend
@savacano28 savacano28 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team technical improvement Technical refactor or improvement is needed and removed bug use for describing something not working as expected labels Mar 5, 2025
@savacano28 savacano28 mentioned this issue Mar 5, 2025
Merged
6 tasks
@savacano28 savacano28 changed the title Refactor code in Atommic/Scenario/Report/Simulation Popover Refactor code in Atomic/Scenario/Report/Simulation Popover Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs triage use to identify issue needing triage from Filigran Product team technical improvement Technical refactor or improvement is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@savacano28