LabTechUDF / LabTechUDF/interfaces-usuario

Bug: Event confirmation page displays raw JSON instead of formatted event details

Open
#36 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Preconditions:
An authorized email and an event has been created and user navigates to the "Confirmar Dados do Evento" page.

**Steps to Reproduce:

Create a new event with valid data (title, description, participants, etc.).
Navigate to the confirmation page: .../event/confirm-data?eventId=.
Observe the event details displayed.

Expected Result:

Event data should be displayed in a structured, readable format with clear labels (e.g., Title, Description, Participants, Date).
JSON should be parsed and rendered into proper UI components (e.g., cards, lists, or tables).
Optional fields should be hidden or displayed as “N/A” instead of showing empty values ("" or {}).

Actual Result:

Page shows raw JSON output directly (see screenshot).
Data is not organized, making it hard for users to confirm event details.
Empty or irrelevant fields (logo: {}, "trilhaDesc": "") are displayed.

Severity:

Severity: Medium (blocks usability — users cannot clearly review event details).

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the /event/confirm-data?eventId= confirmation-page entry point and trace how the event response is rendered. Replace the raw JSON display with structured labeled event details, while omitting empty or irrelevant optional fields. Done means users can review title, description, participants, date, and other available data in a readable format.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.