Journey report regression

[Maxime-J]

Describe the Bug

Starting from 2.16, if you create a journey report without specifying start and end steps, the request doesn't succeed: Zod is rejecting it.

It can be temporarily bypassed by filling and erasing the steps fields so that the request includes empty strings.

Database

MySQL

Relevant log output

{
    "error": {
        "issues": [
            {
                "code": "invalid_type",
                "expected": "string",
                "received": "undefined",
                "path": [
                    "startStep"
                ],
                "message": "Required"
            },
            {
                "code": "invalid_type",
                "expected": "string",
                "received": "undefined",
                "path": [
                    "endStep"
                ],
                "message": "Required"
            }
        ],
        "name": "ZodError",
        [...]
        "errors": [
            {
                "code": "invalid_type",
                "expected": "string",
                "received": "undefined",
                "path": [
                    "startStep"
                ],
                "message": "Required"
            },
            {
                "code": "invalid_type",
                "expected": "string",
                "received": "undefined",
                "path": [
                    "endStep"
                ],
                "message": "Required"
            }
        ]
    }
}

Which Umami version are you using? (if relevant)

2.16.1

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[mikecao]

I think the bug is the start and end steps weren't required before. What is the expected output without defined steps?

[Maxime-J]

Exactly, and all paths are shown when the steps are not defined, like in the release notes
https://github.com/umami-software/umami/releases/tag/v2.12.0

Empty strings are now needed to match the previous behaviour, which breaks the reports without defined steps.