-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat(resources): client-side search #223
Conversation
apps/picsa-apps/dashboard/src/app/modules/resources/pages/home/resources.page.html
Outdated
Show resolved
Hide resolved
apps/picsa-apps/dashboard/src/app/modules/resources/resources.module.ts
Outdated
Show resolved
Hide resolved
const routes: Routes = [{ path: '', component: SearchComponent, title: 'Search' }]; | ||
|
||
@NgModule({ | ||
// declarations:[SearchComponent], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit(non-blocking)
If code isn't required it is better to delete rather than comment out. If there is really good reason to keep (e.g. you know for sure it will be required in near-future) then that should be included in a comment - but usually you can still just delete and if needed in the future recover.
apps/picsa-tools/resources-tool/src/app/pages/resources/search.component.ts
Outdated
Show resolved
Hide resolved
apps/picsa-tools/resources-tool/src/app/pages/resources/search.component.ts
Outdated
Show resolved
Hide resolved
apps/picsa-tools/resources-tool/src/app/pages/resources/search.component.ts
Outdated
Show resolved
Hide resolved
apps/picsa-tools/resources-tool/src/app/pages/resources/search.component.html
Outdated
Show resolved
Hide resolved
apps/picsa-tools/resources-tool/src/app/pages/home/home.component.html
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR
Apologies review is a bit rushed, I haven't tested the feature locally yet, but please see a few inline comments that I think would be good to address first and then we can move onto a more in-depth review after
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR
Apologies review is a bit rushed, I haven't tested the feature locally yet, but please see a few inline comments that I think would be good to address first and then we can move onto a more in-depth review after
Good afternoon @chrismclarke . I have pushed new changes including the requested fixes, let me know if you have any feedback when you review them. I was also need clarification on whether to make the search results clickable and if yes what should be returned when clicked. |
…client-side-search
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Pamella014 for making all the changes. Can confirm all is working as expected on my side.
For the question of what search results should link to, that turned out to be a more difficult question because we have 3 different types of resources that all behave differently (links, collections and files).
To try and simplify things I've made the search results divide by the 3 types, and then was able to reuse the existing components to handle display. Most these changes added in 3aa005, see video below for demo
PICSA.1.webm
I think this is now good to go, there's a few minor changes which I think would be nice to have, but I'll communicate these in a follow-up
Thanks for demo @chrismclarke , looks great |
Description
created a new feature for searching through available resources
Feed Discussion
Requesting for feedback on the search results UI
closes #206
Screenshots / Videos
Updated 2024-01-30
PICSA.1.webm
Original