RocketChat / RocketChat/EmbeddedChat

Fix HTML closing tag typo in playground error display

Open Beginner friendly
#1,182 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
165
Forks
381
Avg merge
1d 2h
Merged PRs (30d)
1

Description

There is a typo in the HTML closing tag used in the printResult() function within the playground files. The closing tag is used instead of , which breaks the HTML structure and prevents error messages from rendering correctly in the output element.

Affected Files

playground.js — Line 58
playground.js — Line 45

Current Code (Broken)

outputElement.innerHTML = <code> Error: ${escapedMessage} Stack: ${escapedStack}</co>;

Expected Code (Fixed)

outputElement.innerHTML = <code> Error: ${escapedMessage} Stack: ${escapedStack}</code>;

Steps to Reproduce

Navigate to the playground files in the auth or api packages.
Trigger an error within the playground.
Observe the output element.

Expected Behavior
Error messages should render correctly inside a HTML element, with properly matched opening and closing tags.

Actual Behavior
The HTML markup is malformed due to the incorrect closing tag (), which prevents the error output from being displayed correctly.

Severity
Low — This issue only affects the playground development/testing utility and does not impact production code.

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

Open the playground.js files in the auth and api packages and inspect the printResult() function around lines 45 and 58. Trigger an error in each playground to reproduce the malformed output, then verify that the error and stack render inside a correctly matched code element.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.