-
Notifications
You must be signed in to change notification settings - Fork 761
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
Integrate search resource selection #13008
Integrate search resource selection #13008
Conversation
c731c48
to
f982e74
Compare
Build Artifacts
|
@pcenov - this is not urgent, but depending on how time consuming your laptop reset process is, this could go to the top of your list for Friday or Monday. Thank you! |
Hi @AlexVelezLl and @marcellamaki - I confirm that the search is integrated as specified above. Here are a few general observations based on my testing which can probably be tracked as follow-up issues if not already tracked somewhere else:
3 There are quite a few design differences if the current implementation is closely compared to Figma such as the back arrow and the label are not centered, the keywords label should be removed, the icons for the categories are not added etc. Since I am not sure if this is in scope for this PR I am just mentioning it here as a consideration:
not.clear.how.to.proceed.mp4
|
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.
Overall the changes are looking good. I left a handful of largely non-blocking comments. Happy to chat further about anything I noted.
I haven't finished going through every file yet, so I will be coming back to give a few parts another closer look
}, | ||
computed: { | ||
isTopic() { | ||
return !this.content.isLeaf; | ||
}, | ||
headingElement() { | ||
return this.headingLevel ? `h${this.headingLevel}` : 'h3'; |
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.
Non-blocking: given the default value of headingLevel
the conditional could be removed here.
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.
Done!
...ugins/coach/assets/src/views/lessons/LessonResourceSelectionPage/LessonContentCard/index.vue
Show resolved
Hide resolved
...ugins/coach/assets/src/views/lessons/LessonResourceSelectionPage/LessonContentCard/index.vue
Show resolved
Hide resolved
Thanks @pcenov!
I think the icons are still not available cc: @marcellamaki, so probably should be reported in a different issue. And the border-bottom in the side panel modal header I think its something we have in develop but not in the figma specs. (honestly I am not sure neither about the reason of this difference but it has been accepted for a long time 😅 cc: @marcellamaki)
|
Thank @AlexVelezLl,
|
22dc161
to
26db2b8
Compare
Hi @pcenov! I have pushed some changes to open the search results just after clicking on a filter. Also I think I have fixed the wrong positioning of the bottom bar when we open the side panel in a mobile device, could you give it a check, please? 😃 |
Thanks @AlexVelezLl - I confirm that now selecting a filter bring the user to the search results and that the "Save & Finish" button is no longer covered by the device's taskbar. I was able to identify one additional mobile issue - the filter by categories is not working in mobile view. This can be replicated both in Chrome's emulator and in an actual device: cannot.select.a.category.in.mobile.view.mp4As always, let me know if this is not in scope for this PR and I'll file a follow-up issue. |
@pcenov @AlexVelezLl - I wonder if this Categories bug on mobile is related to the other one (which I don't remember where it popped up, actually.... last week). But it was I think a discussion of the |
Yes @marcellamaki, its the same, once that one is fixed, this will be fixed automatically :). I think we didnt end up with any follow up actions in that conversation 😅. |
Ah okay - I will open an issue then and we can put it in the backlog for the meeting today. Thank you for remembering Alex :) |
And back to answer questions on a few other points:
I think that is it on the remaining questions that you both had? So, both are important but neither blocking for this PR. And, I am in process of re-reviewing this PR for code review and will add any additional code comments in a little while :) |
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.
Hi @AlexVelezLl - I've added a few comments, I don't think any of them are blocking but more just thoughts and points of discussion. I'll do one more re-review, but then I think we will probably be able to go ahead with approving and merging this!
...ugins/coach/assets/src/views/lessons/LessonResourceSelectionPage/LessonContentCard/index.vue
Show resolved
Hide resolved
...oach/assets/src/views/lessons/LessonSummaryPage/sidePanels/LessonResourceSelection/index.vue
Show resolved
Hide resolved
@@ -13,7 +13,7 @@ | |||
icon="delete" | |||
size="mini" | |||
class="filter-chip-button" | |||
@click="$emit('removeItem', item)" | |||
@click="$emit('removeItem', item, { isLast: items.length === 1 })" |
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.
is this to indicate that there are no more search chips and so in addition to removing the item we want to.... change something else about the UI?
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.
Yes, I did it to save us a tick from redirecting back. The main "thing" here is that searchTerms
gets its value directly from the route query, that means that we need the route query to be updated to have its value updated, so it will "cost" a couple of ticks more before we have the displayingSearchResults
prop to be false and then to redirect.
An alternative could be just to watch displayingSearchResults
and wait until it is false to do the redirectBack, but wanted to be more proactive, save a couple of ticks (I mean, not waiting until displayingSearchResults
gets updated) and be explicit in the code that the last item being removed will redirect us back.
I've done a little bit more manual QA, and I noticed what seems like a rather specific edge case, but searching at the "all channels" level, if I navigate into a folder within the search, the "back to search results" returns me to the main seleciton index, not the search results. (This isn't the case with search results that are within a channel or folder) Screen.Recording.2025-01-31.at.1.51.16.PM.mov |
e9575f3
to
696cfa9
Compare
Thanks @marcellamaki! I hadnt realized that case existed, I have just fixed it, and rebased my PR :) |
const searchFetch = { | ||
data: useSearchObject.results, | ||
loading: useSearchObject.searchLoading, | ||
hasMore: computed(() => !!useSearchObject.more.value), |
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.
Can this be reduced just to hasMore: computed(() => useSearchObject.more.value)
?
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.
Hi @ozer550! In this case its not the same, because hasMore
should be a boolean value, and useSearchObject.more.value
is an object, the "more" object. So to transform it to boolean we can do either !!useSearchObject.more.value
or Boolean(useSearchObject.more.value)
, but personally I like more the former 😅.
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.
Thank you @AlexVelezLl - I think all feedback has been addressed now. While I suspect Peter and Radina may find a few more things when we do full QA of this feature, I think this is in good shape to merge, and we can handle any follow up issues as they come. 🎉
Summary
Compartir.pantalla.-.2025-01-15.17_44_57.mp4
References
Closes #12987
Reviewer guidance