feat: extend travel mode filter selection to use selected_as_default property

[jonasbrunvoll]

Closes https://github.com/AtB-AS/kundevendt/issues/17912

Background

FRAM and NFK have requested that some transport mode filters should be unchecked by default in both app and travel planner web. This request highlights a need that we need to address. As the number of organizations in the OMS grows, it becomes increasingly more difficult to find on singel transport mode configuration that will work well for all orgnaizations. Therefore, each organization should be able to configure their own desired default transportModes.

The requests from AtB, FRAM and NFK are as following:

• AtB: All transport mode filters should be checked by default (7/7).
• NFK: All transport mode filters except flight should be check by default (6/7).
• FRAM: All transport mode filters except flight and train should be checked by default (5/7).
• TROMS: All transport mode filters should be checked by default (7/7).
• Innlandet: All transport mode filters except flight and train should be checked by default (5/7).

Illustrations

screenshots/video/figma

NFK

FRAM

AtB

Proposed solutionfinder

• Add a function to determine whether the selectedAsDefault property is set for each filter.

Acceptence criteria

• The correct transport mode filters are checked by default.
• The user is still able to specify which transport mode filters to use during the search.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
planner-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 8, 2024 9:57am

[mortennordseth]

LGTM! 🎉