The attached program in hitpoint2024 has two values in the room dimension: Lautapelialue and Lautapelialue, aktiviteettinurkka.
The Kompassi backend now knows it should omit Lautapelialue if it is included in Lautapelialue, aktiviteettinurkka when determining the value for the location attribute.
Furthermore, there may be a freeform override or additional specifier in the location attribute in the future. The location attribute always contains what the program manager intended to be displayed independently of the values of the room dimension.
The guide, however, would seem to be manually combining room dimension value titles with ", ". Can you switch to using the location attribute of ScheduleItem instead?
The attached program in
hitpoint2024
has two values in theroom
dimension:Lautapelialue
andLautapelialue, aktiviteettinurkka
.The Kompassi backend now knows it should omit
Lautapelialue
if it is included inLautapelialue, aktiviteettinurkka
when determining the value for thelocation
attribute.Furthermore, there may be a freeform override or additional specifier in the
location
attribute in the future. Thelocation
attribute always contains what the program manager intended to be displayed independently of the values of theroom
dimension.The guide, however, would seem to be manually combining
room
dimension value titles with", "
. Can you switch to using thelocation
attribute ofScheduleItem
instead?NB: A deprecated
location
attribute is provided inProgram
, but it is not recommended to be used in any new things. See https://github.com/con2/kompassi/blob/aa7f3e70108c07febc3319406d44a2154ea75fe9/backend/program_v2/graphql/program_limited.py#L36-L45