Skip to content

RFC: Requirements for Attending Events #2

Description

@deniz-blue

EventInstance or Event should have information about what is required to attend the event (or the specific instance)

Various attendance requirements are, but not limited to:

  • None
  • Must buy a ticket (bought online or physically)
  • Must be part of a group or organization
  • Must fill a form (like a registration form)
  • Age restrictions

The main issue is, there might be more complex logic surrounding this. How do you model something such as "to attend you must either be part of our club or fill the form and buy a ticket" -> club_member || (filled_form && bought_ticket)

We can probably achieve this in one of two ways:

  • Flat array of requirements + logic seperated

    requirements: [
      { type: "part of group", id: "club_member" },
      { type: "form", id: "filled_form" },
      { type: "ticket", id: "bought_ticket" },
    ],
    logic: "club_member || (filled_form && bought_ticket)", // could be AST form
  • Nested objects

    requirements: {
      or: [
        ...,
        { and: [..., ...] }
      ]
    }
    

I will keep this issue open in case anyone comes with a better idea, because both of these approaches seem not great

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions