[🐛 Bug]: Applications crash when the filter component fails to match values.

[ashrafchowdury]

Report

When a user attempts to filter data and the filter component cannot find any matching values, the application crashes unexpectedly. This behaviour is consistent across all the pages that utilize the filter component.

Expected behavior

The application should display a message indicating that no matching values were found, or it should provide a message. It should not crash.

Steps to reproduce the problem

1. Open the application and go to the filter component.
2. Observe where the issue is rising.
3. After finding the issue, add an error handler to that particular function or component.
4. Raise a Popup error message to tell the user that the given value isn't available.

Another Way:

1. Add a condition to filter component to check the values before applying it.

Logs (if applicable)

ashrafChowdury_pezzola_bbug_preview.mp4

Pezzo version

latest one

How do you use Pezzo?

Pezzo Cloud

[ashrafchowdury]

I would like to work on this issue if everything sounds good.

[arielweinberger]

Feel free to work on it @ashrafchowdury. Instead of an error message, it's better to populate empty values of display an empty state.

[ashrafchowdury]

I got it.

It would be great if you could assign the issue to me so I can start working on it freely.

[ashrafchowdury]

Hay @arielweinberger, I am encountering errors while attempting to run the application locally. I have carefully followed the local setup guide, but I am still unable to start the project.

Get this error after running npx nx serve console

---

Should I have to set any environment variables to run the project?

[zhangchengwen629]

我也遇到了PS D:\woker\pezzo\pezzo> npx nx serve console

NX No access token found

Nx will continue running, but nothing will be written or read from the remote cache.
Run details will also not be available in the Nx Cloud UI.

NX Running target serve for project console and 1 task it depends on:

————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

nx run pezzo:"graphql:generate"

[email protected] graphql:generate
nx graphql:generate server

NX No access token found

Nx will continue running, but nothing will be written or read from the remote cache.
Run details will also not be available in the Nx Cloud UI.

NX Running target graphql:generate for project server and 3 tasks it depends on:

nx run server:"prisma:generate" [existing outputs match the cache, left as is]

Environment variables loaded from .env
Prisma schema loaded from apps\server\prisma\schema.prisma

✔ Generated Prisma Client (5.1.1 | binary) to .\node_modules@prisma\client in 123ms

✔ Generated Prisma NestJS/GraphQL to .\apps\server\src@generated in 1.19s
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

nx run server:"graphql:schema-generate"

'GITHUB_ACTIONS' �����ڲ����ⲿ���Ҳ���ǿ����еij���
���������ļ���
Warning: run-commands command "GITHUB_ACTIONS=true npx ts-node -P apps/server/tsconfig.app.json -r tsconfig-paths/register apps/server/scripts/generate-graphql-schema.ts" exited with non-zero status code

NX Running target graphql:generate for project server and 3 tasks it depends on failed

Failed tasks:

• server:graphql:schema-generate

Hint: run the command with --verbose for more details.

NX Running target serve for project console and 1 task it depends on failed

Failed tasks:

• pezzo:graphql:generate

Hint: run the command with --verbose for more details.