-
-
Notifications
You must be signed in to change notification settings - Fork 361
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
Refactor: SearchBar - splitting into smaller components #3883
Labels
$$
~51-150usd
A-refactoring
Refactoring stuff, make code more readable, mitigating tech debt
A-search
related to search components
p3
non-core, affecting less than 40%
Comments
petersopko
added
$$
~51-150usd
A-search
related to search components
A-refactoring
Refactoring stuff, make code more readable, mitigating tech debt
p2
core functionality, or is affecting 60% of app
labels
Aug 30, 2022
This was referenced Aug 30, 2022
Closed
👋 |
ASSIGNED - @Jarsen136 🔒 LOCKED -> Friday, September 2nd 2022, 13:19:56 UTC -> 72 hours |
ASSIGNMENT EXPIRED - @Jarsen136 has been unassigned. |
Reopen this since we introduce unused code (row, columns, filters & switch) in Landing & Navbar. |
17 tasks
yangwao
added
p3
non-core, affecting less than 40%
and removed
p2
core functionality, or is affecting 60% of app
labels
Jan 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
$$
~51-150usd
A-refactoring
Refactoring stuff, make code more readable, mitigating tech debt
A-search
related to search components
p3
non-core, affecting less than 40%
Currently, our search SearchBar.vue is at 909 lines of code (bad, hard to debug etc.)
We'd like to see this split up into smaller components, to give an easily demonstrated example, there are at least three different logical chunks I could see being components:
Somebody with previous experience in similar refactor efforts could pick this up, go over the code and find more elegant solution to our current SearchBar.vue implementation.
The text was updated successfully, but these errors were encountered: