-
Notifications
You must be signed in to change notification settings - Fork 43
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/1 sync people filter and search #7
Fix/1 sync people filter and search #7
Conversation
2e48698
to
e8138dc
Compare
Video looks good. Sorry one more thing. We have reverted our backend api calls from api.people-test->people.test. So we no longer will require the "api" in front of the call. Can you push another commit? I think that'll trigger our github actions workflows for testing. Also in the future, you can run the tests locally as well using: |
e8138dc
to
cfae158
Compare
Checking tests |
@YLeight fix Jest and Prettier issues |
423af48
to
83038fe
Compare
All checks pass. @elraphty |
I think is better to create new branch from new master as it was updated forcily |
9073d03
to
d4cb4d4
Compare
@ecurrencyhodler @elraphty And here we go again |
d4cb4d4
to
767b6c4
Compare
@ecurrencyhodler @elraphty kindly reminder |
Great work @YLeight, it works well, but the user search by alias call is supposed to make a backend call so it can be a global search, and not an array search check |
Are you about this place, right? |
Or about this? |
@elraphty Or do you mean its would be better to rewrite old logic with usage of |
Seems like in this case the util function is no more needed, and I can remove is as a legacy code. To avoid not recommended usage in the future. @elraphty Are we on the same page? |
yeah, we don't need the util function for searching it will only filter 100 users, the people API endpoint already can search if a search query is passed, you can leave the util function for just the skills filter, we will also move the filter search to the backend later, but it is not related to this issue. |
I've used
I've got observed |
9aa3405
to
fa678a1
Compare
@elraphty Tricky content test id on loading conditional rendering Ready for review As I've noticed on a meeting, it seems like languages query string should be persistent (stored in a main store) Can check after P.S. Thanks for patience =) Was too excited) |
@YLeight The endpoint is up and running https://people-test.sphinx.chat/people?search=Evan, can you confirm from your end that it works? |
Tested it, this and my findings from this Demo https://www.loom.com/share/7dc68d5af5ab48c3a81382f770c18a6c
|
Seems like backend is again unavailable |
I do this every day already) |
Okay awesome! do you want to remove this PR from draft? I"m also going to increase your bounties due to the extra work you did. This bounty went from 300k->400k. https://community.sphinx.chat/bounty/1268 Thanks Yegor. |
Hook incapsulate responsibility for filtering people list implicitly by search query (with mobx), and explicitly by coding languages (with react state) Reates: stakwork#1
Add annotations related to filtering functionality by coding language's
`SearchTextInput` doesn't use this prop in any way. It relys on value from store, copied to local react state
`SearchTextInput` doesn't sync local state with original store value This reason any store updates (e.g. initialization from local storage) will be skipped without force re-render of it's parent component. To provide consistent independent behaviour from any parent context add `useEffect` for synchronization
…people page and other routes" This reverts commit cf9997c.
Today, this request |
1d4ce59
to
51cc006
Compare
Implemented uploading synced with filter and search result |
Handle searching and filtration together
Fix: #1
https://jam.dev/c/0c3e8498-5e22-43d5-b81c-a4a8f526af85