You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Case: Ropecon has many additional fields that should be shown in the Guide, for example:
ropecon2023_workshop_fee: Työpajamaksu
ropecon2022_content_warnings: Listaa tähän ohjelmasi sisältämät aiheet, jotka voivat aiheuttaa joillekin osallistujille epämiellyttäviä tuntemuksia tai ahdistusta.
ropecon2023_other_accessibility_information: Muu saavutettavuus
How do we request these fields from the GraphQL API dynamically and how do we know, where to show them (popup content area vs. popup meta area)?
The text was updated successfully, but these errors were encountered:
knomepasi
changed the title
As a program manager I want to define which fields are show in the Guide
As a program manager I want to define which fields are shown in the Guide
May 27, 2024
In the V2 data model, these fields belong in the otherFields. We also need to provide an ontology about them (event.program.otherFieldsSchema or something) ie. localized field titles, expected data types, public/sensitive and display settings such as "please show this on the detail page".
In the V1 to V2 transitional period, we should define the mapping from V1 flags (ropecon20XX_*) to otherFields in the importer.
Case: Ropecon has many additional fields that should be shown in the Guide, for example:
ropecon2023_workshop_fee
: Työpajamaksuropecon2022_content_warnings
: Listaa tähän ohjelmasi sisältämät aiheet, jotka voivat aiheuttaa joillekin osallistujille epämiellyttäviä tuntemuksia tai ahdistusta.ropecon2023_other_accessibility_information
: Muu saavutettavuusHow do we request these fields from the GraphQL API dynamically and how do we know, where to show them (popup content area vs. popup meta area)?
The text was updated successfully, but these errors were encountered: