# 관련도 정렬 시 추가 재로딩 필요

**URL:** https://meta.discourse.org/t/sorting-by-relevance-needs-additional-reload/300366
**Category:** Bug
**Tags:** search, ai, fixed
**Created:** [3월 21, 2024, 2:36오후 UTC](https://meta.discourse.org/t/sorting-by-relevance-needs-additional-reload/300366 "2024-03-21T14:36:33Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![keegan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/keegan/32/383395_2.png) [@keegan](https://meta.discourse.org/u/keegan)
#### Post date: [5월 30, 2024, 2:50오후 UTC](https://meta.discourse.org/t/sorting-by-relevance-needs-additional-reload/300366/4 "2024-05-30T14:50:34Z")

</div>

@Moin, 보고해 주셔서 감사합니다. 이제 해결되었을 것입니다 🎉

> <https://github.com/discourse/discourse-ai/pull/652>
>
> As mentioned on \[Meta\](https://meta.discourse.org/t/sorting-by-relevance-needs-a…dditional-reload/300366?u=keegan), previously the sort order required a refresh to see the change in state of the AI toggle disabled text.
> 
> After merging https://github.com/discourse/discourse/pull/27247, we get access to the \`sortOrder\`'s tracking context so the changes can be updated properly in the respective getters.
> 
> We also simplify things so that we conditionally show the entire AI results toggle only when it is in an allowed \`searchOrder\`. There are too many edge cases when we show text for each scenario and conditionally showing/hiding the element presents a cleaner UX.

---

_[View the full topic](https://meta.discourse.org/t/sorting-by-relevance-needs-additional-reload/300366)._