PR 1/2 - feat(challenge-filters): add logic to manage language tags selected filters

[otrocadev]

Description of the task

As part of the new filtering system refactor, the challenge filters modal needs support for tag-based filtering. Currently, the challenge-filters-trigger component does not manage tags dynamically and lacks the logic required to retrieve and display them depending on the selected languages.

Important

This task introduces the data flow and logic necessary to enable tag filtering. It prepares the filter system for the next UI-focused step of the parent task #230. This PR focuses on functionality and data handling. Styling improvements will be handled in #231

What does this task aim to accomplish?

The goal is to dynamically retrieve tags based on the languages selected by the user and allow them to be selected as part of the filtering criteria.

To achieve this:

• A language ID → name map is propagated from the language filter component
• Tags are fetched per selected language
• Tags are grouped by language and displayed as selectable checkboxes
• Selected tag IDs are emitted to the parent component when filters are applied

📁 Files changed or created

Changes:

language-filter.component.ts

• Emits language ID → name mapping on initialization

challenge-list-filters.component.ts

• Passes the language map to challenge-filters-trigger

challenge-filters-trigger.component.ts

• Fetches tags per selected language using ChallengeFormService.getTagsByLanguage()
• Groups tags by language name
• Tracks selected tag IDs in draftFilters.tags
• Emits selected tag IDs on Apply
• Restores previously selected tags when reopening the modal

Definition of done

• Tags are fetched dynamically when the filter modal opens based on selected languages
• Tags are grouped and displayed by language name
• Users can select/deselect individual tags
• Selected tag IDs are emitted to the parent via filtersApplied
• Previously selected tags remain checked when reopening the modal

Out of scope in this task

• Persisting filter state across sessions
• UI styling or visual polishing handled in #231

Tests / Verification

Manual verification:
• Selecting languages updates available tags
• Tags appear grouped by language
• Applying filters emits correct tag IDs
• Reopening modal restores selected tags

[JungleGiu]

Nice implementation. I was confused at first since I expected to see the tags appear as I selected languages (I think the modifications to the challenge-filters-trigger template threw me off), but I understand that my PR and yours are strictly related, as you need my implementation to make yours work. Maybe change some details in the PR explanation can help everybody understand this better

Hopefully we won’t encounter too many conflicts during the merging process. I saw that you anticipated this with a parallel event, so it shouldn’t create any major issues. Maybe we can open a future PR to integrate our changes even better.

All tests pass! Approved!

[vaniaferreresteban]

I think the logic of the tagItems should be out of the filter logic, but it's also truth that the filter is who decides what will be challanges... the other components must use this source to manage a single truth, let's discuss tomorrow.

[vaniaferreresteban]

It's true that you need adittional filtering of the tags to display on your branch, the overlap query is needed for now, let's create a tech debt and link that to this pr

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
93.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud