Fix HTML closing tag typo in playground error display
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
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.
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.
- Dominant language
- JavaScript
- Stars
- 165
- Forks
- 381
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RocketChat/EmbeddedChat
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 84/100
RocketChat/EmbeddedChat#1360 · 1 comment ·
-
Permissions change-detection in useFetchChatData is dead — applyPermissions re-runs on every call Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
RocketChat/EmbeddedChat#1317 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
RocketChat/EmbeddedChat#1315 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
RocketChat/EmbeddedChat#1313 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
RocketChat/EmbeddedChat#1294 ·
All issues in RocketChat/EmbeddedChat
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·
-
client-controller-update ta-bot-triage team-money-movement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MetaMask/metamask-mobile#36594 ·