Description
We used to have Query Param for the selected teams. Angular displays multiple values like this: teams=1&teams=2&teams=3. This leads to long and unreadable URLs. We didn't want this, therefore we split the values by a , . This looks like this: teams=1,2,3.
Every time we want to access the team's query params, we have to use split(',') to get every single ID and join(',') to set them.
Centralize this behavior in the Angular router so that the router returns a list of string arrays. The ID shouldn't be parsed in the router. The router should expect ["1", "2", "3"] instead of "1,2,3"
Acceptance Criteria
Description
We used to have Query Param for the selected teams. Angular displays multiple values like this:
teams=1&teams=2&teams=3. This leads to long and unreadable URLs. We didn't want this, therefore we split the values by a,. This looks like this:teams=1,2,3.Every time we want to access the team's query params, we have to use
split(',')to get every single ID andjoin(',')to set them.Centralize this behavior in the Angular router so that the router returns a list of string arrays. The ID shouldn't be parsed in the router. The router should expect
["1", "2", "3"]instead of"1,2,3"Acceptance Criteria