Funnel report does not work for events with spaces in their name

[adriannovella]

Describe the Bug

Hi, I tried to make a funnel report with events like "Home - doing something", run query button fails (console shows something like unhandled exception I think) and button keeps spinning.

I changed the event name to "home-doning-something" and now works. So I guess there is something wrong with the space.

Thanks for this awesome project.

Database

PostgreSQL

Relevant log output

This are the docker logs:

Raw query failed. Code: `42601`. Message: `ERROR: syntax error at or near "{"`
    at $n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7315)
    at $n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6623)
    at $n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6307)
    at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9633)
    at async q (/app/.next/server/pages/api/websites/[websiteId]/values.js:1:2536)
    at async z (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16764)
    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17472)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:618:9)
    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:278:37)
    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:853:17) {
  code: 'P2010',
  clientVersion: '5.22.0',
  meta: [Object]
}
 ⨯ Error [PrismaClientKnownRequestError]:
Invalid `prisma.$queryRawUnsafe()` invocation:


Raw query failed. Code: `42601`. Message: `ERROR: syntax error at or near "{"`
    at $n.handleRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:7315)
    at $n.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/library.js:121:6623)
    at $n.request (/app/node_modules/@prisma/client/runtime/library.js:121:6307)
    at async l (/app/node_modules/@prisma/client/runtime/library.js:130:9633)
    at async q (/app/.next/server/pages/api/websites/[websiteId]/values.js:1:2536)
    at async z (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16764)
    at async U.render (/app/node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:17472)
    at async NextNodeServer.runApi (/app/node_modules/next/dist/server/next-server.js:618:9)
    at async NextNodeServer.handleCatchallRenderRequest (/app/node_modules/next/dist/server/next-server.js:278:37)
    at async NextNodeServer.handleRequestImpl (/app/node_modules/next/dist/server/base-server.js:853:17) {
  code: 'P2010',
  clientVersion: '5.22.0',
  meta: [Object]
}

Which Umami version are you using? (if relevant)

No response

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

docker

[franciscao633]

Confirmed. Thanks for reporting, we will have a fix.

[franciscao633]

This seems to be fixed in the dev branch already. Will be resolved next release.

[adriannovella]

Thanks for the quick response!