eat-api version 2

[COM8]

This aims to restructure the API to make it easier to get access to all required information at once.

This should address #10.

TODO

• Remove the mensa-garching.json folder
• Update to the new prices: https://www.studentenwerk-muenchen.de/mensa/mensa-preise/
  • Mensa Leopoldstraße
  • Mensa Weihenstephan and Mensa Lothstraße
  • Self-Service
• Check if the Self-Service prices match for mensa-garching with the actual prices displayed on-site: Not perfect, but works.
• Fix unit tests
• Change the pricing model to student, staff and guests
• Update CI/CD
• Add canteens.json - a list of all canteens with their location Command for all available canteens #3
• Update README.md to reflect the changes and add example

Examples

The new dish object looks like this:

"dishes": [
    {
        "name": "Ravioli mit Pilzfüllung in pikanter Kräutersauce",
        "prices": {
            "students": {
                "base_price": 1.0,
                "price_per_unit": 0.75,
                "unit": "100g"
            },
            "staff": {
                "base_price": 1.0,
                "price_per_unit": 0.9,
                "unit": "100g"
            },
            "guests": {
                "base_price": 1.0,
                "price_per_unit": 1.05,
                "unit": "100g"
            }
        },
        "ingredients": [
            "Ei",
            "Gl",
            "GlW",
            "Kn",
            "Mi",
            "Sl"
        ],
        "dish_type": "Pasta"
    }
]

And for canteens without different pricing tiers:

"dishes": [
    {
        "name": "Tagessuppe",
        "prices": {
            "students": {
                "base_price": 1.0,
                "price_per_unit": null,
                "unit": null
            },
            "staff": {
                "base_price": 1.0,
                "price_per_unit": null,
                "unit": null
            },
            "guests": {
                "base_price": 1.0,
                "price_per_unit": null,
                "unit": null
            }
        },
        "ingredients": [
            "Gl",
            "Sl"
        ],
        "dish_type": "Tagesgericht"
    },
    {
        "name": "(*) Wirsing-Curry mit Kurkuma CousCous",
        "prices": {
            "students": {
                "base_price": 4.5,
                "price_per_unit": null,
                "unit": null
            },
            "staff": {
                "base_price": 4.5,
                "price_per_unit": null,
                "unit": null
            },
            "guests": {
                "base_price": 4.5,
                "price_per_unit": null,
                "unit": null
            }
        },
        "ingredients": [
            "Gl",
            "Mi",
            "Sl"
        ],
        "dish_type": "Tagesgericht"
    },
    {
        "name": "Pasta Front-Cooking Maccaroni Cheese mit Tomatenstücke",
        "prices": {
            "students": {
                "base_price": 4.9,
                "price_per_unit": null,
                "unit": null
            },
            "staff": {
                "base_price": 4.9,
                "price_per_unit": null,
                "unit": null
            },
            "guests": {
                "base_price": 4.9,
                "price_per_unit": null,
                "unit": null
            }
        },
        "ingredients": [
            "Ei",
            "Gl",
            "Mi",
            "Sf",
            "Sl"
        ],
        "dish_type": "Tagesgericht"
    }
]

[COM8]

Once merged we can update GitHub-Pages to the new prices.

[jpbernius]

This breaks all existing API consumers!

[COM8]

Yes.

[COM8]

I created issues for all projects I know about that use eat-api.

• FMeat.php
• UWP-TUM-Campus-App
• lunch gfz
• eat cli

The plan is to switch to the new format on the 01.01.2020.
Are there any concerns about that?