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 repeated code in TxSegmentElementInput and GetCoordinates #325

Open
katiestahl opened this issue Sep 5, 2024 · 0 comments
Open

refactor repeated code in TxSegmentElementInput and GetCoordinates #325

katiestahl opened this issue Sep 5, 2024 · 0 comments
Assignees
@katiestahl
Labels
cleanup Changes only making code cleaner & do not change how the code works nor the outputs produced (e.g. f good first issue Good for newcomers priority:low Low priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"

Comments

@katiestahl
Copy link
Contributor

there's a lot of repeated code in these components - we should refactor into one reusable component
@katiestahl katiestahl added good first issue Good for newcomers priority:low Low priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup" cleanup Changes only making code cleaner & do not change how the code works nor the outputs produced (e.g. f labels Sep 5, 2024
@katiestahl katiestahl self-assigned this Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@katiestahl katiestahl

Labels
cleanup Changes only making code cleaner & do not change how the code works nor the outputs produced (e.g. f good first issue Good for newcomers priority:low Low priority technical debt A feature/requirement implemented in a sub-optimal way & must be re-written. Contrast to "cleanup"
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@katiestahl