♻️ (frontend) Make the code more readable by simplifying conditional logic

[r00gm]

Use a map to make the code more readable

Purpose

Make the code more readable by simplifying conditional logic.

Proposal

Replaced nested ternary expressions with a mapping object to improve readability and maintainability.

• ♻️ (frontend) Replaced conditional logic for title assignment with a key-based map lookup
• ♻️ (frontend) Improved clarity and made it easier to add more filters in the future

[r00gm]

Minor nitpick.
Couldn't stand the ternary nesting 😅 — replaced with a map before it summoned the ternary demon 😄

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

[Copilot]

Directly indexing the mapping with [target] assumes that target always matches one of the map keys. Consider adding a default fallback (e.g., using the nullish coalescing operator) to prevent 'title' from being undefined for unexpected target values.

Suggested change

	}[target]
	}[target] ?? t('Unknown');

[lunika]

It was just to test how copilot does a review 🙂

Maybe based on the suggestion uses t('All docs') than t('Unknown'). WDYT @AntoLC ?

[r00gm]

i would keep it the way it is.

if someone where to add another key to the enum DocDefaultFilter, typescript will raise an error which will force the addition of a new key to the translation map

[r00gm]

or

Suggested change

	}[target]
	const title = {
	[DocDefaultFilter.MY_DOCS]: t('My docs'),
	[DocDefaultFilter.SHARED_WITH_ME]: t('Shared with me'),
	}[target] ?? t('All docs');