Topic list query params

AI-generated summary

The discussion revolves around routing issues in the TagDrop and CategoryDrop components, where filtering actions redirect to new pages instead of applying query parameters. kaden-stytch notes that selecting a tag or category should use query parameters (e.g., ?tags=development) rather than creating new URLs, as it feels more intuitive for filtering. They also mention difficulties in modifying the components due to their location in the select-kit/addon directory. sam acknowledges the complexity, pointing out the transition between tag-centric and category-centric routing, and suggests simplifying the system by relying solely on ?tags=... for tag filtering, as current routing rules are overly complicated.

Hello! Routing from the TagDrop and CategoryDrop components seems off to me. They feel like they are filters, but they route you to new pages - for example, if I am on the theme component category and select the development tag, it brings me to https://meta.discourse.org/tags/c/theme-component/120/development. I feel like it should be https://meta.discourse.org/c/theme-component/120?tags=development.

Same functionality goes for the CategoryDrop when you are on a tag page (I would expect it to bring you to https://meta.discourse.org/tag/development?category=theme-component).

I added a category and tag header, but they don’t work after filtering with the current routing. I was looking into overriding/modifying the related components, but I’m not sure if it is possible since they are in the select-kit/addon directory.

1 Like

Its not a trivial puzzle, cause:

https://meta.discourse.org/tag/chat/l/latest

Has:

So are you in a transition point between “Tag centric” routing at that point to “category centric routing”

Long term I do wonder if we totally let go of “tag centric” routing and just rely on ?tags=... for all tag filtering of topic lists, cause now the routing rules are just way to elaborate for my liking.

1 Like